camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem jiang <>
Subject Re: CXF consumer endpoint + XSLT + Tracer = EmptyStackException
Date Wed, 13 Nov 2013 04:03:37 GMT
Can you change the CXF endpoint data format from PAYLOAD to MESSAGE just like this ?

<from uri="cxf:bean:OrderService?dataFormat=MESSAGE”/>

If I remember right there was an issue in turn CXF PAYLOAD message into a DOM in camel-2.10.x.

Willem Jiang

Red Hat, Inc.
Blog: ( (English)
 ( (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem

On Tuesday, October 22, 2013 at 5:30 AM, alapaka wrote:

> I suspect it may have to do with the type of object in the message, though It
> does not appear to be an issue with stream caching. I'm a newbie, so my
> grasp of the internals is still superficial.
> I tried stream caching at both context and route level without success.
> Also, there are several steps after the incoming consumer that shows the
> incoming message to be readable more than once.
> It seems to be an issue with the XSLT endpoint; I have encountered a similar
> issue with a wireTap in a route with two XSLT endpoints; having the wireTap
> before the first XSLT endpoint results in the same EmptyStackException -
> funny though because I can have any number of wireTaps after that first XSLT
> endpoint and the second XSLT performs as expected.
> I will do a little more playing around to see if I can isolate this problem
> better - it seems to be related to the CXF consumer at the start of the
> route as well; I am using the default XSLT transformer class, I will try to
> substitute xalan for example.
> aloha
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at (

View raw message