You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by KnutIvar <kn...@gmail.com> on 2010/02/02 11:04:16 UTC
Client side; service returns fault; Unmarshalling Error: unexpected
element
Hi!
I'm trying to call a service, but gets unmarshalling error when I get a
response which (in my eyes) seems valid.
>From the wsdl;
<wsdl:operation name="createAndStartRequestByValue">
<wsdl:input name="createAndStartRequestByValueRequest"
message="omWS-v1-0:createAndStartRequestByValueRequest"/>
<wsdl:output name="createAndStartRequestByValueResponse"
message="omWS-v1-0:createAndStartRequestByValueResponse"/>
<wsdl:fault name="createAndStartRequestByValueException"
message="omWS-v1-0:createAndStartRequestByValueException"/>
</wsdl:operation>
The return message from the service (and now my mock...) looks kind of like
this;
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<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:Body>
</soapenv:Envelope>
However; CXF doesn't like it and gives me the following stacktrace;
org.apache.cxf.interceptor.Fault: Unmarshalling Error: unexpected element
(uri:"http://ossj.org/xml/Management/v1-0", local:"createException").
Expected elements are <{http://ossj.org/xml/Management/v1-0}requestKey>
at
org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:764)
at
org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:623)
at org.apache.cxf.jaxb.io.DataReaderImpl.read(DataReaderImpl.java:128)
at
org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:190)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236)
at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:671)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2177)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2057)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1982)
at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:637)
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:483)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:309)
DefaultValidationEventHandler: [ERROR]: unexpected element
(uri:"http://ossj.org/xml/Management/v1-0", local:"createException").
Expected elements are <{http://ossj.org/xml/Management/v1-0}requestKey>
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:261)
It expects a parameter which is located in the wsdl:output instead of
mapping it to the wsdl:fault.
Do I have to write a custom faultinterceptor in order to handle this, or
could I add a standard interceptor to my client?
Client;
org.apache.cxf.jaxws.JaxWsProxyFactoryBean clientFactory = new
org.apache.cxf.jaxws.JaxWsProxyFactoryBean();
clientFactory.setAddress("http://localhost:8088/soap/services/OrderManagement-mock");
clientFactory.setServiceClass(JVTManagementSessionWSPort.class);
JVTManagementSessionWSPort client =
(JVTManagementSessionWSPort)clientFactory.create();
-----
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-tp27417976p27417976.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Client side; service returns fault; Unmarshalling Error:
unexpected element
Posted by KnutIvar <kn...@gmail.com>.
And the solution; Follow the SOAP specification.... The SOAP fault defines
some tags that has to be part of the soap Fault. ..., and the custom
exception must then be part of the <detail> tag within the fault. ... and
it maps fine.
(chapter 4.4 in http://www.w3.org/TR/2000/NOTE-SOAP-20000508/ this document
)
-----
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-tp27417976p27513094.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Client side; service returns fault; Unmarshalling Error:
unexpected element
Posted by KnutIvar <kn...@gmail.com>.
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
>> dkulp@apache.org
>> 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.
Re: Client side; service returns fault; Unmarshalling Error:
unexpected element
Posted by KnutIvar <kn...@gmail.com>.
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.
>
> Dan
>
>
> On Tue February 2 2010 1:10:51 pm KnutIvar wrote:
>> It looks like this...;
>>
>> <element name="createAndStartRequestByValueException">
>> <complexType>
>> <choice>
>> <element name="ossIllegalArgumentException"
>> type="co-v1-5:OssIllegalArgumentException"/>
>> <element name="remoteException"
>> type="co-v1-5:RemoteException"/> <element name="objectNotFoundException"
>> type="co-v1-5:ObjectNotFoundException"/>
>> <element name="duplicateKeyException"
>> type="co-v1-5:DuplicateKeyException"/>
>> <element name="createException"
>> type="co-v1-5:CreateException"/> </choice>
>> </complexType>
>> </element>
>>
>> As you can see; it has the createExceptionElement as a choice.
>>
>> However; the requestKey appears here;
>>
>> <element name="createAndStartRequestByValueResponse">
>> <complexType>
>> <sequence>
>> <element name="requestKey" type="om-v1-0:RequestKey" />
>> </sequence>
>> </complexType>
>> </element>
>>
>> ... and more about the request (from the wsdl);
>> <wsdl:operation name="createAndStartRequestByValue">
>> <soap:operation soapAction="createAndStartRequestByValue"
>> style="document"/>
>> <wsdl:input name="createAndStartRequestByValueRequest">
>> <soap:body parts="parameters" use="literal"/>
>> </wsdl:input>
>> <wsdl:output name="createAndStartRequestByValueResponse">
>> <soap:body parts="parameters" use="literal"/>
>> </wsdl:output>
>> <wsdl:fault name="createAndStartRequestByValueException">
>> <soap:fault name="createAndStartRequestByValueException" use="literal"/>
>> </wsdl:fault>
>> </wsdl:operation>
>>
>> ... It looks ok to me...
>>
>> dkulp wrote:
>> > What does the schema look like for the
>> > createAndStartRequestByValueException
>> > element? From that error message, it looks like
>> > createAndStartRequestByValueException is not allowed to have a
>> > "createException" child element. The only expected element is a
>> > "requestKey"
>> > element.
>> >
>> > Dan
>>
>> -----
>> http://www.knutivars.net www.knutivars.net
>> "http://www.knutivars.net/cxf/index.html Document first Apache CXF and
>> XMLBeans with Spring.
>>
>
> --
> Daniel Kulp
> dkulp@apache.org
> 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-tp27417976p27425106.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Client side; service returns fault; Unmarshalling Error: unexpected element
Posted by Daniel Kulp <dk...@apache.org>.
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.
Dan
On Tue February 2 2010 1:10:51 pm KnutIvar wrote:
> It looks like this...;
>
> <element name="createAndStartRequestByValueException">
> <complexType>
> <choice>
> <element name="ossIllegalArgumentException"
> type="co-v1-5:OssIllegalArgumentException"/>
> <element name="remoteException"
> type="co-v1-5:RemoteException"/> <element name="objectNotFoundException"
> type="co-v1-5:ObjectNotFoundException"/>
> <element name="duplicateKeyException"
> type="co-v1-5:DuplicateKeyException"/>
> <element name="createException"
> type="co-v1-5:CreateException"/> </choice>
> </complexType>
> </element>
>
> As you can see; it has the createExceptionElement as a choice.
>
> However; the requestKey appears here;
>
> <element name="createAndStartRequestByValueResponse">
> <complexType>
> <sequence>
> <element name="requestKey" type="om-v1-0:RequestKey" />
> </sequence>
> </complexType>
> </element>
>
> ... and more about the request (from the wsdl);
> <wsdl:operation name="createAndStartRequestByValue">
> <soap:operation soapAction="createAndStartRequestByValue"
> style="document"/>
> <wsdl:input name="createAndStartRequestByValueRequest">
> <soap:body parts="parameters" use="literal"/>
> </wsdl:input>
> <wsdl:output name="createAndStartRequestByValueResponse">
> <soap:body parts="parameters" use="literal"/>
> </wsdl:output>
> <wsdl:fault name="createAndStartRequestByValueException">
> <soap:fault name="createAndStartRequestByValueException" use="literal"/>
> </wsdl:fault>
> </wsdl:operation>
>
> ... It looks ok to me...
>
> dkulp wrote:
> > What does the schema look like for the
> > createAndStartRequestByValueException
> > element? From that error message, it looks like
> > createAndStartRequestByValueException is not allowed to have a
> > "createException" child element. The only expected element is a
> > "requestKey"
> > element.
> >
> > Dan
>
> -----
> http://www.knutivars.net www.knutivars.net
> "http://www.knutivars.net/cxf/index.html Document first Apache CXF and
> XMLBeans with Spring.
>
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: Client side; service returns fault; Unmarshalling Error:
unexpected element
Posted by KnutIvar <kn...@gmail.com>.
It looks like this...;
<element name="createAndStartRequestByValueException">
<complexType>
<choice>
<element name="ossIllegalArgumentException"
type="co-v1-5:OssIllegalArgumentException"/>
<element name="remoteException" type="co-v1-5:RemoteException"/>
<element name="objectNotFoundException"
type="co-v1-5:ObjectNotFoundException"/>
<element name="duplicateKeyException"
type="co-v1-5:DuplicateKeyException"/>
<element name="createException" type="co-v1-5:CreateException"/>
</choice>
</complexType>
</element>
As you can see; it has the createExceptionElement as a choice.
However; the requestKey appears here;
<element name="createAndStartRequestByValueResponse">
<complexType>
<sequence>
<element name="requestKey" type="om-v1-0:RequestKey" />
</sequence>
</complexType>
</element>
... and more about the request (from the wsdl);
<wsdl:operation name="createAndStartRequestByValue">
<soap:operation soapAction="createAndStartRequestByValue"
style="document"/>
<wsdl:input name="createAndStartRequestByValueRequest">
<soap:body parts="parameters" use="literal"/>
</wsdl:input>
<wsdl:output name="createAndStartRequestByValueResponse">
<soap:body parts="parameters" use="literal"/>
</wsdl:output>
<wsdl:fault name="createAndStartRequestByValueException">
<soap:fault name="createAndStartRequestByValueException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
... It looks ok to me...
dkulp wrote:
>
>
> What does the schema look like for the
> createAndStartRequestByValueException
> element? From that error message, it looks like
> createAndStartRequestByValueException is not allowed to have a
> "createException" child element. The only expected element is a
> "requestKey"
> element.
>
> Dan
>
> --
> Daniel Kulp
> dkulp@apache.org
> 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-tp27417976p27424872.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Client side; service returns fault; Unmarshalling Error: unexpected element
Posted by Daniel Kulp <dk...@apache.org>.
What does the schema look like for the createAndStartRequestByValueException
element? From that error message, it looks like
createAndStartRequestByValueException is not allowed to have a
"createException" child element. The only expected element is a "requestKey"
element.
Dan
On Tue February 2 2010 5:04:16 am KnutIvar wrote:
> Hi!
>
> I'm trying to call a service, but gets unmarshalling error when I get a
> response which (in my eyes) seems valid.
>
> From the wsdl;
> <wsdl:operation name="createAndStartRequestByValue">
> <wsdl:input name="createAndStartRequestByValueRequest"
> message="omWS-v1-0:createAndStartRequestByValueRequest"/>
> <wsdl:output name="createAndStartRequestByValueResponse"
> message="omWS-v1-0:createAndStartRequestByValueResponse"/>
> <wsdl:fault name="createAndStartRequestByValueException"
> message="omWS-v1-0:createAndStartRequestByValueException"/>
> </wsdl:operation>
>
> The return message from the service (and now my mock...) looks kind of like
> this;
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body>
> <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:Body>
> </soapenv:Envelope>
>
> However; CXF doesn't like it and gives me the following stacktrace;
> org.apache.cxf.interceptor.Fault: Unmarshalling Error: unexpected element
> (uri:"http://ossj.org/xml/Management/v1-0", local:"createException").
> Expected elements are <{http://ossj.org/xml/Management/v1-0}requestKey>
> at
> org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:7
> 64) at
> org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:6
> 23) at org.apache.cxf.jaxb.io.DataReaderImpl.read(DataReaderImpl.java:128)
> at
> org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteral
> InInterceptor.java:190) at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChai
> n.java:236) at
> org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:671) at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleRespons
> eInternal(HTTPConduit.java:2177) at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleRespons
> e(HTTPConduit.java:2057) at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPCon
> duit.java:1982) at
> org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66) at
> org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:637) at
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInte
> rceptor.handleMessage(MessageSenderInterceptor.java:62) at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChai
> n.java:236) at
> org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:483) at
> org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:309)
> DefaultValidationEventHandler: [ERROR]: unexpected element
> (uri:"http://ossj.org/xml/Management/v1-0", local:"createException").
> Expected elements are <{http://ossj.org/xml/Management/v1-0}requestKey>
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:261)
>
> It expects a parameter which is located in the wsdl:output instead of
> mapping it to the wsdl:fault.
> Do I have to write a custom faultinterceptor in order to handle this, or
> could I add a standard interceptor to my client?
>
> Client;
> org.apache.cxf.jaxws.JaxWsProxyFactoryBean clientFactory = new
> org.apache.cxf.jaxws.JaxWsProxyFactoryBean();
> clientFactory.setAddress("http://localhost:8088/soap/services/OrderManageme
> nt-mock"); clientFactory.setServiceClass(JVTManagementSessionWSPort.class);
> JVTManagementSessionWSPort client =
> (JVTManagementSessionWSPort)clientFactory.create();
>
> -----
> http://www.knutivars.net www.knutivars.net
> "http://www.knutivars.net/cxf/index.html Document first Apache CXF and
> XMLBeans with Spring.
>
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog