[jbossws-issues] [JBoss JIRA] Commented: (JBWS-2308) faultCode argument for createFault was passed NULL

[Alessio Soldano (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBWS-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12439332#action_12439332 ] 

Alessio Soldano commented on JBWS-2308:
---------------------------------------

The reason for this stands in JAXP implementation being used. In particular the problem is caused by an error in the namespace output when performing message transformation to DOMResult. See http://issues.apache.org/jira/browse/XALANJ-2382 .

> faultCode argument for createFault was passed NULL
> --------------------------------------------------
>
>                 Key: JBWS-2308
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2308
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-metro
>    Affects Versions:  jbossws-metro-3.0.3
>            Reporter: Alessio Soldano
>            Assignee: Alessio Soldano
>             Fix For: jbossws-metro-3.0.5
>
>
> When using client logical handlers and throwing SOAPFaultException from one of them after having accessed the message's payload through the LogicalMessageContext, we get the following exception during exception unmarshalling:
> java.lang.IllegalArgumentException: faultCode argument for createFault was passed NULL
> 	at com.sun.xml.messaging.saaj.soap.ver1_1.SOAPFactory1_1Impl.createFault(SOAPFactory1_1Impl.java:87)
> 	at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:179)
> 	at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:130)
> 	at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
> 	at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
> 	at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
> This causes a different runtime exception to received on the client (instead of the one created by the handler).
> This also causes the following cts tests to fail:
> com/sun/ts/tests/jaxws/api/javax_xml_ws_handler/LogicalHandler/Client.java#ClientLogicalOutboundHandleFaultFalseTest_from_wsappclient
> com/sun/ts/tests/jaxws/api/javax_xml_ws_handler/LogicalHandler/Client.java#ClientLogicalOutboundHandleFaultFalseTest_from_wsejb
> com/sun/ts/tests/jaxws/api/javax_xml_ws_handler/LogicalHandler/Client.java#ClientLogicalOutboundHandleFaultFalseTest_from_wsservlet
> com/sun/ts/tests/jaxws/api/javax_xml_ws_handler/LogicalHandler/Client.java#ServerLogicalInboundHandleFaultFalseTest_from_wsappclient
> com/sun/ts/tests/jaxws/api/javax_xml_ws_handler/LogicalHandler/Client.java#ServerLogicalInboundHandleFaultFalseTest_from_wsejb
> com/sun/ts/tests/jaxws/api/javax_xml_ws_handler/LogicalHandler/Client.java#ServerLogicalInboundHandleFaultFalseTest_from_wsservlet
> com/sun/ts/tests/jaxws/api/javax_xml_ws_handler_soap/SOAPHandler/Client.java#ClientSOAPOutboundHandleMessageThrowsSOAPFaultExceptionTest_from_wsappclient
> com/sun/ts/tests/jaxws/api/javax_xml_ws_handler_soap/SOAPHandler/Client.java#ClientSOAPOutboundHandleMessageThrowsSOAPFaultExceptionTest_from_wsejb
> com/sun/ts/tests/jaxws/api/javax_xml_ws_handler_soap/SOAPHandler/Client.java#ClientSOAPOutboundHandleMessageThrowsSOAPFaultExceptionTest_from_wsservlet 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira