cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <dk...@apache.org>
Subject Re: WS-RM Message part CreateSequence was not recognized.
Date Fri, 02 Nov 2007 17:31:18 GMT
Bharath,

Instead of creating the JAXB context from the package name, I've changed 
it to creating via the actual ObjectFactory.class object.   Thus, this 
MAY be fixed with the latest snapshots.

That said, I'm not sure why it's not working for you.   The 
org.apache.cxf.ws.addressing.v200408.ObjectFactory class is definitely 
in the jar.   Maybe a classpath issue?    ContextClassloader issue?   I 
don't really know.  

Dan


On Thursday 01 November 2007, Bharath Ganesh wrote:
> The actual cause seems to be this:
>
> [ Trace - 26 ]    ; SOAP_HEADER_ENCODE_FAILURE_MSG
> javax.xml.bind.JAXBException: "org.apache.cxf.ws.addressing.v200408"
> doesnt contain ObjectFactory.class or jaxb.index
>     at
> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java
>
> :119)
>
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:39)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
>     at java.lang.reflect.Method.invoke(Method.java:585)
>     at
> javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:132) at
> javax.xml.bind.ContextFinder.find(ContextFinder.java:286) at
> javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372) at
> javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337) at
> javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:244) at
> org.apache.cxf.ws.addressing.VersionTransformer$Names200408.getJAXBCon
>text( VersionTransformer.java:345)
>     at
> org.apache.cxf.ws.addressing.VersionTransformer.getExposedJAXBContext
> (VersionTransformer.java:284)
>     at
> org.apache.cxf.ws.addressing.soap.MAPCodec.encode(MAPCodec.java:153)
> at
> org.apache.cxf.ws.addressing.soap.MAPCodec.mediate(MAPCodec.java:128)
> at org.apache.cxf.ws.addressing.soap.MAPCodec.handleMessage(
> MAPCodec.java:110)
>     at org.apache.cxf.ws.addressing.soap.MAPCodec.handleMessage(
> MAPCodec.java:73)
>     at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
> PhaseInterceptorChain.java:207)
>     at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:254)
>     at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:205)
>     at org.apache.cxf.ws.rm.Proxy.invoke(Proxy.java:247)
>     at org.apache.cxf.ws.rm.Proxy.createSequence(Proxy.java:162)
>     at org.apache.cxf.ws.rm.RMManager.getSequence(RMManager.java:316)
>     at
> org.apache.cxf.ws.rm.RMOutInterceptor.handle(RMOutInterceptor.java
>
> :129)
>
>     at org.apache.cxf.ws.rm.AbstractRMInterceptor.handleMessage(
> AbstractRMInterceptor.java:78)
>     at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
> PhaseInterceptorChain.java:207)
>     at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:254)
>     at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:205)
>     at
> org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73) at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java
>
> :135)
>
> -Bharath
>
> On 11/1/07, Bharath Ganesh <bharathganesh@gmail.com> wrote:
> > Hi
> >
> > I have been running across a strange error for quite some time. I
> > have enabled RM, using RM-Assertions in the WSDL.
> > The client sends a createSequence message to the server endpoint.
> > The Server responds back with a soap fault:
> >  Interceptor has thrown exception, unwinding now
> > org.apache.cxf.interceptor.Fault: Message part
> > {http://schemas.xmlsoap.org/ws/2005/02/rm}CreateSequence
> > <http://schemas.xmlsoap.org/ws/2005/02/rm%7DCreateSequence> was not
> > recognized.
> >     at
> > org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(
> > DocLiteralInInterceptor.java:178)
> >     at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
> > PhaseInterceptorChain.java :207)
> >     at org.apache.cxf.transport.ChainInitiationObserver.onMessage(
> > ChainInitiationObserver.java:73)
> >     at
> > org.apache.cxf.transport.servlet.ServletDestination.doMessage(
> > ServletDestination.java:79)
> >     at
> > org.apache.cxf.transport.servlet.ServletController.invokeDestination
> > ( ServletController.java:319)
> >     at org.apache.cxf.transport.servlet.ServletController.invoke(
> > ServletController.java:224)
> >     at
> > org.apache.cxf.transport.servlet.CXFServlet.invoke(CXFServlet.java
> >
> > :284)
> >
> >     at org.apache.cxf.transport.servlet.CXFServlet.doPost
> > (CXFServlet.java
> >
> > :262)
> >
> > The outgoing message at the client side is:
> >
> > <soap:Envelope
> > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><C
> >reateSequence xmlns=" http://schemas.xmlsoap.org/ws/2005/02/rm"
> > xmlns:ns2="http://schemas.xmlsoap.org/ws/2004/08/addressing
> > "><AcksTo><ns2:Address>
> > http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</ns2
> >:Address></AcksTo><Expires>PT0S</Expires><Offer><Identifier>urn:uuid:
> >cb64b637-afa8-4395-be29-004d2ff90401</Identifier><Expires>PT0S</Expir
> >es></Offer></CreateSequence></soap:Body></soap:Envelope>
> >
> >
> > Earlier the same test used to work fine. At that time the
> > createsequence soap message was:
> >
> > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/
> > "><soap:Header><MessageID
> > xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">urn:uuid:f8
> >e71725-c8e9-49e3-860c-e214f434f610</MessageID><To xmlns="
> > http://schemas.xmlsoap.org/ws/2004/08/addressing">
> > http://localhost:8181/cart/cart</To><ReplyTo xmlns="
> > http://schemas.xmlsoap.org/ws/2004/08/addressing"><Address>http://sc
> >hemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
> > </Address></ReplyTo><FaultTo xmlns="
> > http://schemas.xmlsoap.org/ws/2004/08/addressing"><Address>http://sc
> >hemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</Address></Fau
> >ltTo><Action xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing
> > ">
> > http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence
> > </Action></soap:Header>
> > <soap:Body><ns2:CreateSequence xmlns="
> > http://schemas.xmlsoap.org/ws/2004/08/addressing"
> > xmlns:ns2="http://schemas.xmlsoap.org/ws/2005/02/rm
> > "><ns2:AcksTo><Address>
> > http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</Add
> >ress></ns2:AcksTo><ns2:Expires>PT0S</ns2:Expires><ns2:Offer><ns2:Iden
> >tifier>urn:uuid:f7c604f6-7822-4499-8bbe-edb4b4ed5127</ns2:Identifier>
> ><ns2:Expires>PT0S</ns2:Expires></ns2:Offer></ns2:CreateSequence></soa
> >p:Body></soap:Envelope>
> >
> >
> >
> > If you looks the the two soap messages, the soap message where the
> > createSequence was not recognized by the server, did not contain a
> > SOAP header. Is this the problem? If so, what could be the reason
> > for this?
> >
> > Any help would be appreciated.
> > -Bharath



-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194
daniel.kulp@iona.com
http://www.dankulp.com/blog

Mime
View raw message