This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Used "netbeans-ent_pack-5_5_1-gavotte-070208_28-windows.exe" with JDK 1.5.0_10 on XP. Test Case : http://blogs.sun.com/pcmreddy/resource/StockQuoteCA_files/StockQuoteCA2.html After completing BPEL editing Run BPEL JUnit test case. Change the value in input file as "SUNW" This is the stock quote we are requesting here. Observe test case execution failed with the following error. PWC3982: Cannot register MBean for the Protocol grizzlyHttpProtocol.selectorRegisterProtocol WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 18181 Exception in processing reply. javax.xml.ws.soap.SOAPFaultException: Server did not recognize the value of HTTP Header SOAPAction: . at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:163) at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:94) at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:174) at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:193) at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.outboundCall(OutboundMessageProcessor.java:585) at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyOutbound(OutboundMessageProcessor.java:272) at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:157) at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:57) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595)
This is reproducible in Build : netbeans-ent_pack-5_5_1-gavotte-070209-windows.exe
Venkat, please assign somebody to to this issue
Alex, could you please take a look at this issue?
This is a runtime issue. I've filed a separate bug, 6524674, to address this issue. It appears that with the move to JAX-WS, we need to specify the SOAP Action URI in a different manner than before. I've fixed the issue, but it will likely not make it to beta. Please track this issue from now on in Bugster with the aforementioned bug number.
Verified 6524674 in bugster and closed.