You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@camel.apache.org by Jens <sm...@dzbank.de> on 2013/09/25 17:10:03 UTC

Mocking CXF service with XSLT

Hi,

I'm trying to "implement" a CXF JAX-WS service using an XSL transformation,
ie.

from("cxf:bean:...").to("xslt:...");

The CXF endpoint has a JMSConfiguration with a replyDestination attached and
I also tried setting exchangePattern=InOut explicitly but unfortunately, in
either case, CXF does not put the reply on the reply queue and the exchange
ends with no output whatsoever.

The last log output I get from CXF is "Invkoing handleMessage on interceptor
org.apache.cxf.interceptor.OutgoingChainInterceptor@XXXXX"

Any idea why the response isn't sent back? Is there anything I need to do to
"prepare" the response message for the CXF endpoint. Fwiw, I also tried
converting the (string) transformation result to a CxfPayload but that
didn't make any difference.

Camel version used is 2.8.4.

Thanks,
Jens



--
View this message in context: http://camel.465427.n5.nabble.com/Mocking-CXF-service-with-XSLT-tp5740205.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Mocking CXF service with XSLT

Posted by Jens <sm...@dzbank.de>.

Jens wrote
> Hi,
> 
> I'm trying to "implement" a CXF JAX-WS service using an XSL
> transformation, ie.
> 
> from("cxf:bean:...").to("xslt:...");
> 
> The CXF endpoint has a JMSConfiguration with a replyDestination attached
> and I also tried setting exchangePattern=InOut explicitly but
> unfortunately, in either case, CXF does not put the reply on the reply
> queue and the exchange ends with no output whatsoever.
> 
> The last log output I get from CXF is "Invkoing handleMessage on
> interceptor org.apache.cxf.interceptor.OutgoingChainInterceptor@XXXXX"
> 
> Any idea why the response isn't sent back? Is there anything I need to do
> to "prepare" the response message for the CXF endpoint. Fwiw, I also tried
> converting the (string) transformation result to a CxfPayload but that
> didn't make any difference.
> 
> Camel version used is 2.8.4.
> 
> Thanks,
> Jens

I think I figured it out. It seems to be related to bugs in the integration
of CXF asynchronous mode again. If I switch the receiving CXF JMS endpoint
to synchronous, this works as expected.

Jens



--
View this message in context: http://camel.465427.n5.nabble.com/Mocking-CXF-service-with-XSLT-tp5740205p5740234.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Mocking CXF service with XSLT

Posted by Christian Posta <ch...@gmail.com>.

Put together a sample route/test case and I can dig into it for you.


On Wed, Sep 25, 2013 at 8:10 AM, Jens <sm...@dzbank.de> wrote:

> Hi,
>
> I'm trying to "implement" a CXF JAX-WS service using an XSL transformation,
> ie.
>
> from("cxf:bean:...").to("xslt:...");
>
> The CXF endpoint has a JMSConfiguration with a replyDestination attached
> and
> I also tried setting exchangePattern=InOut explicitly but unfortunately, in
> either case, CXF does not put the reply on the reply queue and the exchange
> ends with no output whatsoever.
>
> The last log output I get from CXF is "Invkoing handleMessage on
> interceptor
> org.apache.cxf.interceptor.OutgoingChainInterceptor@XXXXX"
>
> Any idea why the response isn't sent back? Is there anything I need to do
> to
> "prepare" the response message for the CXF endpoint. Fwiw, I also tried
> converting the (string) transformation result to a CxfPayload but that
> didn't make any difference.
>
> Camel version used is 2.8.4.
>
> Thanks,
> Jens
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Mocking-CXF-service-with-XSLT-tp5740205.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta