Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Date: Thu, 26 Sep 2013 06:19:40 -0700 (PDT)
From: Jens <smixdev@dzbank.de>
To: users@camel.apache.org
Message-ID: <1380201580021-5740234.post@n5.nabble.com>
In-Reply-To: <1380121803540-5740205.post@n5.nabble.com>
References: <1380121803540-5740205.post@n5.nabble.com>
Subject: Re: Mocking CXF service with XSLT
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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.