[jira] Resolved: (CXF-1575) SoapFault is not being properly propagated up the stack

["Daniel Kulp (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-1575.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.7
                   2.1.1

Added some code to get it to try and do something a bit smarter if an older saaj version is found.



> SoapFault is not being properly propagated up the stack
> -------------------------------------------------------
>
>                 Key: CXF-1575
>                 URL: https://issues.apache.org/jira/browse/CXF-1575
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1
>         Environment: Ubuntu 7.04, Windows XP, jdk 1.5_09,  cxf 2.1
>            Reporter: Alton Idowu
>             Fix For: 2.1.1, 2.0.7
>
>
> We are getting a soap exception
>      org.apache.cxf.binding.soap.SoapFault: [ISS.0088.9125] SOAP request does not conform to the SOAP message model
> that is not being properly propagated up.  Instead we are getting a java.lang.NoSuchMethodError: javax.xml.soap.SOAPFactory.createFault()Ljavax/xml/soap/SOAPFault;
> Looks like the issue is in the JaxWsClientProxy.invoke(Object, Method, Object[]) line: 193	
>             if (getBinding() instanceof HTTPBinding) {
>                 HTTPException exception = new HTTPException(HttpURLConnection.HTTP_INTERNAL_ERROR);
>                 exception.initCause(ex);
>                 throw exception;
>             } else if (getBinding() instanceof SOAPBinding) {
>                 SOAPFault soapFault = ((SOAPBinding)getBinding()).getSOAPFactory().createFault();
>                                                                                                                                                   ^^^^^^^^^^^^^^
> Looks like the SoapFactory returned by the binding does not have a createFault method.  Does this mean that we have the incorrect version of a jar?
> At any rate, the error should be caught so that a the very least a meaningful stack trace will be generated.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.