I tried it ... and it gives me this stack;
java.lang.NullPointerException
at
org.apache.cxf.jaxws.JaxWsClientProxy.createSoapFault(JaxWsClientProxy.java:197)
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:142)
at $Proxy58.createAndStartRequestByValue(Unknown Source)
at my testclass....
(using cxf 2.2.5 btw) ... and the JaxWsClientProxy @ 197 =
if
(!soapFault.getNamespaceURI().equals(((SoapFault)ex).getFaultCode().getNamespaceURI())
&& SOAPConstants.URI_NS_SOAP_1_1_ENVELOPE
.equals(((SoapFault)ex).getFaultCode().getNamespaceURI()))
I'll have a look at it, but I'm not sure about everything here..., so please
assist :)
- KI.
KnutIvar wrote:
>
> So the response should look like this?
>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> <soapenv:Body>
> <soapenv:Fault>
> <om-v1-0:createAndStartRequestByValueException
> xmlns:om-v1-0="http://os.org/xml/Management/v1-0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:co-v1-5="http://os.org/xml/Common/v1-5";
> xmlns:jrc-v2-0="http://jrc.com/ossj/xml/Common/v2-0";>
> <om-v1-0:createException
> xsi:type="jrc-v2-0:JrCreateException">
> <co-v1-5:message></co-v1-5:message>
> <jrc-v2-0:jrExceptionDetails>
> <jrc-v2-0:errorCode>60003</jrc-v2-0:errorCode>
> <jrc-v2-0:retryable>false</jrc-v2-0:retryable>
> <jrc-v2-0:errorMessage>Order state
> invalid.</jrc-v2-0:errorMessage>
>
> <jrc-v2-0:component>com.jr.ordermanager</jrc-v2-0:component>
> <jrc-v2-0:severity>Medium</jrc-v2-0:severity>
> <jrc-v2-0:reason>No subscriber found for
> productExternalID [98802-1]</jrc-v2-0:reason>
>
> <jrc-v2-0:requestPrimaryKey>936</jrc-v2-0:requestPrimaryKey>
> </jrc-v2-0:jrExceptionDetails>
> </om-v1-0:createException>
> </om-v1-0:createAndStartRequestByValueException>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
>
> I think I did try that........ and it gave me a similar exception...
> I'll try more.. (don't have the full environment on the current computer).
>
> Thank you!
>
>
> dkulp wrote:
>>
>>
>> Oh. You are putting what should be in a soap:Fault into the soap:Body.
>> Since it's not a soap:Fault, it's trying to process it as a reponse, not
>> a
>> fault. Thus, the message really isn't valid. If it's a fault, it
>> shoudl be
>> a soap:Fault.
>>
>> Daniel Kulp
>> [email protected]
>> http://www.dankulp.com/blog
>>
>>
>
-----
http://www.knutivars.net www.knutivars.net
"http://www.knutivars.net/cxf/index.html Document first Apache CXF and
XMLBeans with Spring.
--
View this message in context:
http://old.nabble.com/Client-side--service-returns-fault--Unmarshalling-Error%3A-unexpected-element-tp27417976p27426269.html
Sent from the cxf-user mailing list archive at Nabble.com.
