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.212.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=d9dVw6sb+CXPv3tFBXBVpvbPS4+5hNQlTIinzTAUazNV0nXJNxZ+e7RxVgcHm/TuuE
         z8YkXjc7RVJBJ4VQjzmwDXN/o69U+gTmxUubE8JqdVsqZflC5PlrMqGUy8oK10TDBdX5
         3Jy6ITJztJrBbnDGycLyyvMhMSPxXyecnBKp4=
Message-ID: <4BB5C99A.5070200@gmail.com>
Date: Fri, 02 Apr 2010 18:40:26 +0800
From: Willem Jiang <willem.jiang@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: users@camel.apache.org
Subject: Re: issue with HTTP response content length being set to CXF request
 length - causing truncated responses.
References: <270858e91003011122t3d3e3453k4f1ef642216c9b4f@mail.gmail.com>
 <ABECCE27-B7E7-464B-831A-ABA017BE629E@gmail.com> <4B8C879D.70309@gmail.com>
 <270858e91003072237n7f694dbence767bcf73d3c7ea@mail.gmail.com>
 <28088048.post@talk.nabble.com> <4BB2A6B8.6060608@gmail.com>
 <28092929.post@talk.nabble.com> <4BB32D07.7070409@gmail.com>
 <28107784.post@talk.nabble.com> <4BB4B21A.8020405@gmail.com>
 <28111197.post@talk.nabble.com> <4BB53962.3050400@gmail.com>
 <28117551.post@talk.nabble.com>
In-Reply-To: <28117551.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

The url is OK, I can see the latest Camel 2.3.0-SNAPSHOT was published 
yesterday, maybe you can try to run the test again.

Willem

zigo wrote:
> Willem,
> 
> I am not sure I got your question right, anyway I have downloaded version
> 2.3-SNAPSHOT from the Apache Snapshots repository at
> https://repository.apache.org/content/repositories/snapshots
> 
> Alberto
> 
> 
> 
> 
> willem.jiang wrote:
>> Hi,
>>
>> I'm doing the daily development of camel on the MacOSX.
>> Can you tell me how do get the Camel 2.3.0-SNAPSHOT ?
>> It will be helpful for use to trace the issue.
>>
>> Willem
>>
>> zigo wrote:
>>> What platform are you testing on?
>>>
>>> I have seen that this problem manifests only on MacOS, tests done on
>>> Windows
>>> work without removing the Content-Length.
>>>
>>> Anyway, I will try compiling the trunk.
>>>
>>> Alberto
>>>
>>>
>>>
>>> willem.jiang wrote:
>>>> Hi,
>>>>
>>>> Can you build the trunk code yourself ?
>>>> My test is working[1], I'm doubt there are something wrong with SNAPSHOT 
>>>> publish.
>>>>
>>>> [1] http://svn.apache.org/viewvc?rev=929475&view=rev
>>>>
>>>> Willem
>>>>
>>>> zigo wrote:
>>>>> Willem,
>>>>>
>>>>> I have tried with the latest 2.3-SNAPSHOT, but unfortunately the
>>>>> problem
>>>>> is
>>>>> still there.
>>>>>
>>>>> Alberto
>>>>>
>>>>>
>>>>> willem.jiang wrote:
>>>>>> FYI, I create a JIRA[1] for this issue and committed a quick fix for
>>>>>> it.
>>>>>> Please feel free to check out the latest Camel 2.3.0-SNAPSHOT to
>>>>>> verify
>>>>>> it.
>>>>>>
>>>>>> Willem
>>>>>>
>>>>>> zigo wrote:
>>>>>>> Willem,
>>>>>>>
>>>>>>> my route is this:
>>>>>>>
>>>>>>> <camelContext id="camel"
>>>>>>> xmlns="http://camel.apache.org/schema/spring">
>>>>>>> 		<route>
>>>>>>> 			<from
>>>>>>> uri="cxf:bean:gtEndpoint?serviceName={http://foo.com}gt_connector&amp;dataFormat=MESSAGE"/>
>>>>>>> 			
>>>>>>> 			<!-- Workaround to a Camel bug -->
>>>>>>> 			<removeHeader headerName="Content-Length" />
>>>>>>> 			<convertBodyTo type="String" />
>>>>>>> 			<to
>>>>>>> uri="jms:GT.IN?replyTo=GT.OUT&amp;deliveryPersistent=false&amp;useMessageIDAsCorrelationID=true"
>>>>>>> />
>>>>>>> 		</route>
>>>>>>> 	</camelContext>
>>>>>>>
>>>>>>> I think this issue should be considered a bug, or at least pointed
>>>>>>> out
>>>>>>> in
>>>>>>> Camel documentation.
>>>>>>>
>>>>>>> Alberto
>>>>>>>
>>>>>>>
>>>>>>> willem.jiang wrote:
>>>>>>>> We filter the message header of "Content-Length" from camel to cxf.
>>>>>>>> If you just pass the message to the other camel endpoint, I'm afraid
>>>>>>>> you 
>>>>>>>> need to remove it you self.
>>>>>>>>
>>>>>>>> Willem
>>>>>>>>
>>>>>>>> zigo wrote:
>>>>>>>>> I am still having the same problem using:
>>>>>>>>>
>>>>>>>>> - Camel 2.2.0
>>>>>>>>> - CXF 2.2.6
>>>>>>>>> - Mac OS 10.6.2
>>>>>>>>>
>>>>>>>>> Workaround (removing http header) works for me.
>>>>>>>>>
>>>>>>>>> Alberto
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> wkeenan wrote:
>>>>>>>>>> On Tue, Mar 2, 2010 at 3:35 AM, Willem Jiang
>>>>>>>>>> <willem.jiang@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi
>>>>>>>>>>> Can you check out the latest released Camel 2.2.0 ?
>>>>>>>>>>>
>>>>>>>>>> working on  camel 2.2.0,  CXF 2.2.6 on Mac10.6
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Wayne
>>>>>>>>>>
>>>>>>>>>>
>>>>
>>
>>
>