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: domain of willem.jiang@gmail.com
 designates 209.85.160.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=DKxgSH0eS4oNpGGtHAQ1rbZYOKMcHhmLMjapZdBmvVzOLtLM11dkxcPP/NWNItJxjQ
         QpHFPpdktOot5KnoGYhnJxr4evyWbB9LHqAZp8FGnwetpQcCl6qMwtNLwiQtV8j6wQ1S
         c4qCgNnyb8GSUkQygaxB9XwPFP1zJ+Lm6wVOQ=
Message-ID: <4CCE587D.2080807@gmail.com>
Date: Mon, 01 Nov 2010 14:04:45 +0800
From: Willem Jiang <willem.jiang@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: users@camel.apache.org
Subject: Re: CXF, Camel Transport, and "Can't find InputStream in message"
References: <AANLkTikxBvg+uZAq_qJaWWwLxkXOtX9UU+-SZ0KuYFb0@mail.gmail.com>
	<4CC2ED97.6010609@gmail.com>
 <AANLkTikLsRrJzzEe8jqLyqh8O+L6GbNbt6EDRSkkdWAT@mail.gmail.com>
In-Reply-To: <AANLkTikLsRrJzzEe8jqLyqh8O+L6GbNbt6EDRSkkdWAT@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

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<willem.jiang@gmail.com>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