Kind of messed up on the properties retrieval as the message can hold
multiple properties.
Do:
AddressingProperties ap = ContextUtils.retrieveMAPs(
message, false, true);
(and if that doesn't work, flip the middle false to true)
That should grab the correct addressing properties.
Dan
On Monday, June 25, 2012 02:55:54 PM Daniel Kulp wrote:
> On Monday, June 25, 2012 06:18:26 PM Marco Pas wrote:
> > Hi Aki,
> >
> > Thanks for your reply, the clients is sending the ws addressing
> > property in the wrong way. It is build expecting to get synchronous
> > feedback, but it send a replyTo field filled with content making the
> > call asynchronous. So the HTTP 202 is returned.
> > So i was looking for ways on skipping the HTTP 202, but it seems that
> > if i modifing the replyto header field should make it ok. Looking for
> > a way to modify the replyTo property and make it synchronous, whatever
> > the client is sending.
> > I am aware that this is a rather strange solution and we should fix
> > the client, but that is not in my reach to do so.
>
> Any easy way may be to add an interceptor on the server's incoming chain
> to basically do:
>
> AddressingProperties ap = message.get(AddressingProperties.class);
> ap.setReplyTo(...)
> with an anonymous EPR.
>
> If that runs at the end of the PRE_PROTOCOL or prior to the PRE_LOGICAL
> phase, (USER_PROTOCOL may make the mose sense) it should allow you to
> modify the replyto address that the runtime sees.
>
> Dan
>
> > Grtz
> >
> > 2012/6/25 Aki Yoshida <[email protected]>:
> > > Hi Marco,
> > > Is your client expecting some specific response message in the http
> > > response?
> > >
> > > The HTTP 202 response code is used for the HTTP response for a oneway
> > > service call that returns no content or a request-response service
> > > call, where the real response is configured to be sent back to another
> > > port.
> > >
> > > I am not sure about your scenario. Is your client a oneway service
> > > client that can't handle the HTTP 202 and expects the HTTP 200 with an
> > > empty content or an empty SOAP envelope? Or it is a request-response
> > > service client?
> > >
> > > regards, aki
> > >
> > > 2012/6/25 Marco Pas <[email protected]>:
> > >> Hi there, i am looking for ways to skip the HTTP 202 reponse send
> > >> back
> > >> by CXF when using WS Addressing.
> > >> We need to support clients that are not capable of handling the HTTP
> > >> 202 response. The operate in a request-response mode and not
> > >> are not able to handle the HTTP 202 returned by CXF.
> > >>
> > >> Is there any way to skip the HTTP 202 reponse ?
> > >>
> > >> /Marco
--
Daniel Kulp
[email protected] - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
