Hi Jérémie,
I just applied your patch, it's a part of Camel 2.6-SNAPSHOT now.
On 10/24/10 12:22 AM, Jérémie wrote:
I have created CAMEL-3269
https://issues.apache.org/activemq/browse/CAMEL-3269
On Sat, Oct 23, 2010 at 4:13 PM, Willem Jiang<[email protected]>wrote:
Current camel-cxf component just treat the MEP as InOut, so you can get the
such error.
Please feel free to create a JIRA[1], so we can keep track of this issue.
[1]https://issues.apache.org/activemq/browse/CAMEL
On 10/23/10 7:34 PM, Jérémie wrote:
Hello,
I'm using a jaws proxy with camel transport for cxf in order to
implement a webservice.
Sometimes cxf can't process the response of the camel route, and fail
with "Can't find InputStream in message". after some research, i suppose
it's a conflict with CamelConduit and the MEP of the message :
- CamelConduit, through CxfMessageHelper.getCxfInMessage is looking for
the Out message of the exchange
- When the route has only one processor like<choice>,<setBody>,
<transform>, the Out part of the exchange is empty, and so cxf fail
- When the route is a pipeline, the in message is automatically copied
to the out message, so cxf successfully handle the message
i have attached a test-case and a simple patch, but I'm not sure that
it's the proper way to correct this error : In getCxfInMessage, if there
is no out part in the current exchange, i take the in part. Maybe the
CamelConduit should use a ProducerTemplate and not a processor instance…
Or maybe I'm not using it the proper way :)
Jeremie
--
Willem
----------------------------------
Open Source Integration: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: http://twitter.com/willemjiang
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
