cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <dk...@apache.org>
Subject Re: CXF and xstream: Unmarshalling Error
Date Tue, 24 Sep 2013 21:27:02 GMT

I really don't know much about the stream stuff.   It SOUNDS like it's doing something to
the class loader or similar to make it not find the proper package-info.class.   My suggestion
would be to add the -xjc-npa flag to the CXF code generation to get all the information moved
out of the package-info and into each annotation.   That may help.

Dan


On Sep 24, 2013, at 7:52 AM, nicolas_mugnier <nmugnier@gnubila.fr> wrote:

> Hi all,
> 
> Context:
> We are having some troubles with CXF (2.7.5) and xstream on Tomcat 7.
> The CXF libraries and xstream used by the webapps are in a common folder.
> We've got several webapps that invoke our CXF web services.
> We also have a webapp that needs to be initialized on tomcat startup. This
> webapp needs to use xstream.
> 
> Troubles:
> Tomcat starts, the webapp that needs to be initialized on startup is
> initialized and loads the xstream library. 
> If we invoke a CXF Web Service, we are getting a SOAPFaultException
> (Unmarshalling Error). The stacktrace is available at the end of this
> message.
> However, if the webapp is not initialized on startup, we can invoke our web
> services. The deployment of this webapp after having invoked (at least once)
> our web services, doesn't not generate exception.
> 
> Thanks in advance for your help,
> Nicolas
> 
> Stacktrace:
> /Caused by: org.apache.cxf.binding.soap.SoapFault: Unmarshalling Error:
> unexpected element (uri:"http://pandora.maatg.fr/ns/sal",
> local:"directoryURL"). Expected elements are <{}directoryURL>
>        at
> org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:84)
> ~[cxf-rt-bindings-soap-2.7.5.jar:2.7.5]
>        at
> org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:51)
> ~[cxf-rt-bindings-soap-2.7.5.jar:2.7.5]
>        at
> org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:40)
> ~[cxf-rt-bindings-soap-2.7.5.jar:2.7.5]
>        at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
> ~[cxf-api-2.7.5.jar:2.7.5]
>        at
> org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:113)
> ~[cxf-api-2.7.5.jar:2.7.5]
>        at
> org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:69)
> ~[cxf-rt-bindings-soap-2.7.5.jar:2.7.5]
>        at
> org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:34)
> ~[cxf-rt-bindings-soap-2.7.5.jar:2.7.5]
>        at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
> ~[cxf-api-2.7.5.jar:2.7.5]
>        at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:800)
> ~[cxf-api-2.7.5.jar:2.7.5]
>        at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1592)
> ~[cxf-rt-transports-http-2.7.5.jar:2.7.5]
>        at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1490)
> ~[cxf-rt-transports-http-2.7.5.jar:2.7.5]
>        at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1309)
> ~[cxf-rt-transports-http-2.7.5.jar:2.7.5]
>        at
> org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
> ~[cxf-api-2.7.5.jar:2.7.5]
>        at
> org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:622)
> ~[cxf-rt-transports-http-2.7.5.jar:2.7.5]
>        at
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
> ~[cxf-api-2.7.5.jar:2.7.5]
>        at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
> ~[cxf-api-2.7.5.jar:2.7.5]
>        at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:530)
> ~[cxf-api-2.7.5.jar:2.7.5]
>        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:463)
> ~[cxf-api-2.7.5.jar:2.7.5]
>        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:366)
> ~[cxf-api-2.7.5.jar:2.7.5]
>        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:319)
> ~[cxf-api-2.7.5.jar:2.7.5]
>        at
> org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
> ~[cxf-rt-frontend-simple-2.7.5.jar:2.7.5]
>        at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:133)
> ~[cxf-rt-frontend-jaxws-2.7.5.jar:2.7.5]
>        ... 9 common frames omitted 
> /
> 
> 
> 
> --
> View this message in context: http://cxf.547215.n5.nabble.com/CXF-and-xstream-Unmarshalling-Error-tp5734429.html
> Sent from the cxf-dev mailing list archive at Nabble.com.

-- 
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com


Mime
View raw message