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.
As suggested by developer I am raising this bug here, Refer 6525580 in bugster for developer comments : Steps to Reproduce : 1. Created the XSLT project. 2. Created the Composite application. 3. Deploy the Composite application. 4. Create the testcase and modify the input.xml with invalid data. 5. Observe that it throws Nullpointer exception. 6. Projects are attached for your reference. Below is output and appserver, build details : Exception in processing reply. java.lang.NullPointerException at com.sun.xml.ws.util.QNameMap.getEntry(QNameMap.java:462) at com.sun.xml.ws.util.QNameMap.get(QNameMap.java:135) at com.sun.xml.ws.model.wsdl.WSDLBoundPortTypeImpl.getOperation(WSDLBoundPortTypeImpl.java:188) at com.sun.xml.ws.model.wsdl.WSDLBoundPortTypeImpl.getOperation(WSDLBoundPortTypeImpl.java:44) at com.sun.xml.ws.api.message.Message.getOperation(Message.java:258) at com.sun.xml.ws.api.message.Message.getOperation(Message.java:267) at com.sun.xml.ws.api.message.Message.isOneWay(Message.java:333) at com.sun.xml.ws.api.message.Packet.createServerResponse(Packet.java:630) at com.sun.xml.ws.server.provider.ProviderArgumentsBuilder.getResponse(ProviderArgumentsBuilder.java:23) at com.sun.xml.ws.server.provider.AsyncProviderInvokerTube$AsyncProviderCallbackImpl.sendError(AsyncProviderInvokerTube.java:81) at com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider.onReply(AsyncJBIProvider.java:252) at com.sun.jbi.httpsoapbc.MessageExchangeSupport.notifyOfReply(MessageExchangeSupport.java:90) at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyInbound(OutboundMessageProcessor.java:186) at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:155) 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) Received ERROR status for exchange: 121365697388068-20985-133908570005000109 App Server details: App Server version = Sun Java System Application Server 9.1 (build b 35-rc) App Server build date = Wed Feb 07 00:50:20 PST 2007 JBI details: ________________________________________________________________________________ _______ Running at 15 February 2007 10:50:26 AM on Windows XP 5.1 [x86] using Java 1.5.0 _09-b03 from c:\progra~1\java\jdk1.5.0_09\jre app server type = GLASSFISH (sub-type = CLUSTER version = 91) app server domains = 1 (instances = 0 cluster = ) java.io.tmpdir = C:\DOCUME~1\rn162588\LOCALS~1\Temp\ jbi port = 17888 (secure = true) installed product build = 070213_5 installed product variant = Kenai installed product kit type = image JBI build details: JBI Framework build date = Tue Feb 13 16:47:52 PST 2007 [source: c://gf91/ jbi/lib/jbi_framework.jar] HTTP SOAP Binding build date = Tue Feb 13 10:29:36 PST 2007 [source: c://gf91/ jbi/components/com.sun.httpsoapbc-1.0-2/httpsoapbc.jar] BPEL Engine build date = Tue Feb 13 10:30:24 PST 2007 [source: c://gf91/ addons/jbi-components/bpelserviceengine.jar] NetBeans build details: Netbeans IDE build = 070213_26 Netbeans IDE version = 200702130600 [source: c://netbe ans/5.5.1/build_info] Netbeans IDE build date = Tue Feb 13 09:03:58 PST 2007 [source: c://netbe ans/5.5.1/platform6/core/core.jar] CAPS Modules build date = Tue Feb 13 19:38:54 PST 2007 [source: c://netbe ans/5.5.1/soa1/ant/nblib/org-netbeans-modules-compapp-projects-jbi.jar]
Created attachment 38586 [details] XSLT module
Created attachment 38587 [details] Composite application
Reassigning to Enterprise for evaluation.
With the wrong input data in the attached jbi project (element with no namespace), the test driver never gets a reply back (due to the NPE) and simply times out. With a different type of wrong input data (wrong element with namespace, say, replacing "<Name>Hello</Name>" in the input file by "<new:Foo>Hello</new:Foo>"), the test driver does get a soap fault message back (<faultstring>javax.jbi.messaging.MessagingException: Failed to normalize input. Could not normalize message did not find any node matching the element name, Name in the soap message Reported Cause: did not find any node matching the element name, Name in the soap message</faultstring>). So it looks like HTTP SOAP BC needs to catch the NPE and returns a soap fault for the no-namespace case. I am closing this as INVALID as there is nothing to fix in compapp project or test driver. I will add comment to the bugster ticket.
Verified in the build NetBeans IDE 6.0 Build 200703191900 and observed that it work's fine and hence marked as verified.