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: http://camel.465427.n5.nabble.com/CXF-consumer-endpoint-XSLT-Tracer-EmptyStackException-tp5741942p5742003.html Sent from the Camel - Users mailing list archive at Nabble.com.
