Hi Eoghan,
Yes, the client SOAPUi allows to do that. I have a new error now :
Console of the client
Fri Feb 12 18:07:57 CET 2010:INFO:StartSequence Request Sent:
2e7dfecf-f888-45c6-8c21-5a10038ea9bc
Fri Feb 12 18:08:02 CET 2010:INFO:Sequence response Received, sequence ID:
on karaf
18:08:02,828 | WARN | 5457...@qtp1-0 | PhaseInterceptorChain |
ache.cxf.common.logging.LogUtils 361 | Interceptor has thrown exception,
unwinding now
org.apache.cxf.binding.soap.SoapFault: The value of wsrm:Identifier is not a
known Sequence identifier.
at
org.apache.cxf.ws.rm.soap.SoapFaultFactory.createSoap11Fault(SoapFaultFactory.java:78)
at
org.apache.cxf.ws.rm.soap.SoapFaultFactory.createFault(SoapFaultFactory.java:68)
at
org.apache.cxf.ws.rm.AbstractRMInterceptor.handleMessage(AbstractRMInterceptor.java:92)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:109)
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:312)
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:276)
at
org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:70)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:741)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:213)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
Caused by: org.apache.cxf.ws.rm.SequenceFault: The value of wsrm:Identifier
is not a known Sequence identifier.
at
org.apache.cxf.ws.rm.SequenceFaultFactory.createUnknownSequenceFault(SequenceFaultFactory.java:39)
at
org.apache.cxf.ws.rm.Destination.acknowledge(Destination.java:103)
at
org.apache.cxf.ws.rm.RMInInterceptor.processSequence(RMInInterceptor.java:145)
at
org.apache.cxf.ws.rm.RMInInterceptor.handle(RMInInterceptor.java:94)
at
org.apache.cxf.ws.rm.AbstractRMInterceptor.handleMessage(AbstractRMInterceptor.java:78)
Regards,
Charles
Eoghan Glynn-4 wrote:
>
> Hi Charles,
>
> The CloseSequence protocol is new in WS-RM 1.1 (
> http://docs.oasis-open.org/ws-rx/wsrm/200702)
>
> CXF currently supports WS-RM 1.0
> (http://schemas.xmlsoap.org/ws/2005/02/rm).
>
> Hence the non-recognition of the CloseSequence message.
>
> Is your client/message originator using WS-RM 1.1? Can it be configured to
> use 1.0 instead?
>
> Cheers,
> Eoghan
>
> On 12 February 2010 13:17, cmoulliard <[email protected]> wrote:
>
>>
>> Hi,
>>
>> I have configured CXF 2.2.5 with Apache Camel to process Web Services
>> using
>> the spec WS-RM. I receive this message in the log of the application
>> server
>> (Apache Felix Karaf) :
>>
>> ID: 5
>> Address: /cxf/camel-example/incident
>> Encoding: ISO-8859-1
>> Content-Type: text/xml
>> Headers: {content-type=[text/xml], Host=[localhost:8080],
>> Content-Length=[618], User-Agent=[Jakarta Commons-HttpClient/3.1],
>> accept-encoding=[gzip,deflate], Content-Type=[text/xml]}
>> Payload: <soapenv:Envelope
>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Header
>> xmlns:wsa="http://www.w3.org/2005/08/addressing";><wsa:Action>
>> http://docs.oasis-open.org/ws-rx/wsrm/200702/CloseSequence
>> </wsa:Action><wsa:MessageID>uuid:af62b9a5-b5f3-4bef-a36b-edd13dd8059d</wsa:MessageID><wsa:To>
>> http://localhost:8080/cxf/camel-example/incident</wsa:To></soapenv:Header>
>> <soapenv:Body
>> xmlns:wsrm="http://docs.oasis-open.org/ws-rx/wsrm/200702
>> "><wsrm:CloseSequence><wsrm:LastMsgNumber>1</wsrm:LastMsgNumber><wsrm:Identifier>soap:Client</wsrm:Identifier></wsrm:CloseSequence></soapenv:Body>
>> </soapenv:Envelope>
>> --------------------------------------
>> 13:54:44,359 | WARN | 17713...@qtp2-2 | PhaseInterceptorChain
>> |
>> ache.cxf.common.logging.LogUtils 361 | Interceptor has thrown exception,
>> unwinding now
>> org.apache.cxf.interceptor.Fault: Message part
>> {http://docs.oasis-open.org/ws-rx/wsrm/200702}CloseSequence<http://docs.oasis-open.org/ws-rx/wsrm/200702%7DCloseSequence>was
>> not
>> recognized. (Does it exist in service WSDL?)
>> at
>>
>> org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:186)
>> at
>>
>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236)
>> at
>>
>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:109)
>> at
>>
>> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:312)
>> at
>>
>> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:276)
>> at
>>
>> org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:70)
>> at
>> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
>> at
>>
>> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
>> at
>> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
>> at org.mortbay.jetty.Server.handle(Server.java:324)
>> at
>> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
>> at
>>
>> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
>> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:741)
>> at
>> org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:213)
>> at
>> org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
>> at
>>
>> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
>> at
>>
>> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
>>
>> It seems that there is something missing in the WSDL but if I compare my
>> wsdl with one provided with the example I don't see any difference.
>>
>> Any idea is welcome ?
>>
>> Regards,
>>
>> Charles
>>
>> -----
>> Charles Moulliard
>> SOA Architect
>>
>> My Blog : http://cmoulliard.blogspot.com/
>> http://cmoulliard.blogspot.com/
>> --
>> View this message in context:
>> http://old.nabble.com/CloseSequence-was-not-recognized.--%28Does-it-exist-in-service-WSDL-%29-tp27563431p27563431.html
>> Sent from the cxf-user mailing list archive at Nabble.com.
>>
>>
>
>
-----
Charles Moulliard
SOA Architect
My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/
--
View this message in context:
http://old.nabble.com/CloseSequence-was-not-recognized.--%28Does-it-exist-in-service-WSDL-%29-tp27563431p27566625.html
Sent from the cxf-user mailing list archive at Nabble.com.
