On Wednesday, February 15, 2012 12:29:39 PM Guy Pardon wrote:
> Thanks,
>
> But isn't there a way to avoid an interceptor here? I mean, getting access
> to the resulting SOAP response message in the client?
By default, we stream and thus the resulting SOAP message doesn't exist. You
can configure in the SAAJInInterceptor to build up the SAAJ model, but you
would then still need a very small interceptor that would just do:
message.put("some.key", message.getContent(Docuement.class))
(I think)
to copy it from contents and into the message properties that would be passed
back to the client.
Dan
>
> Guy
>
> On 15-feb-2012, at 10:44, Freeman Fang wrote:
>
> Hi,
>
> You can write a customer inInterceptor for client side to do anything you
> want, of course include the XPath filter operation. If your requirement is
> too complex, Apache Camel[1] is more suitable to do it.
>
> [1]http://camel.apache.org/
>
> Freeman
>
> On 2012-2-15, at 下午4:19, Guy Pardon wrote:
> > Hi,
> >
> > Any pointers on how I can write a JAXWS client that uses XPath to filter
> > the response from a service? For instance, to extract only the known
> > content, like in consumer-driven contracts.
> >
> > Thanks
> > Guy
>
> ---------------------------------------------
> Freeman Fang
>
> FuseSource
> Email:[email protected]
> Web: fusesource.com
> Twitter: freemanfang
> Blog: http://freemanfang.blogspot.com
--
Daniel Kulp
[email protected] - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
