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 hzbarcea@gmail.com designates
 209.85.213.45 as permitted sender)
Message-ID: <502020F8.2040102@gmail.com>
Date: Mon, 06 Aug 2012 15:54:32 -0400
From: Hadrian Zbarcea <hzbarcea@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: users@camel.apache.org
Subject: Re: URISupport.normalizeUri different result from camel 2.8.2 to
 2.10.0
References: <1343748069925-5716633.post@n5.nabble.com>
 <CALhQg-YO_k3ALQNTLp7fAm7PedVetFpA4acZ5GOcjS3mJpO32A@mail.gmail.com>
 <1344243883011-5716870.post@n5.nabble.com>
 <CALhQg-aLa5DPmLwO2r+gNRcvoN=b5fgSoj1cwr1q9pgfVzCrXw@mail.gmail.com>
 <1344252882370-5716877.post@n5.nabble.com>
In-Reply-To: <1344252882370-5716877.post@n5.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Would using properties be acceptable as a solution (including 
camel-jasypt maybe if you don't want the pwd in clear)?

Hadrian

On 08/06/2012 07:34 AM, Marco Crivellaro wrote:
>
> hekonsek wrote
>>
>> Ok. The good news is that I got a workaround for you :) .
>>
>> Create the component without the FTP password defined in the
>> parameters and then programatically set it on the endpoint.
>>
>
> I wish it was this easy... unfortunately our architecture is build around
> the endpoint uris (a third component provides the URIs), it is very
> difficult to apply your workaround (which is smart I have to say).
> I'll see if I can apply it using interceptors (which we already use to set
> filename).
>
> Thanks
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/URISupport-normalizeUri-different-result-from-camel-2-8-2-to-2-10-0-tp5716633p5716877.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>