Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: neutral (nike.apache.org: 216.139.236.26 is neither permitted
 nor denied by domain of marco.crive@gmail.com)
Date: Mon, 6 Aug 2012 04:34:42 -0700 (PDT)
From: Marco Crivellaro <marco.crive@gmail.com>
To: users@camel.apache.org
Message-ID: <1344252882370-5716877.post@n5.nabble.com>
In-Reply-To: 
 <CALhQg-aLa5DPmLwO2r+gNRcvoN=b5fgSoj1cwr1q9pgfVzCrXw@mail.gmail.com>
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>
Subject: Re: URISupport.normalizeUri different result from camel 2.8.2 to
 2.10.0
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


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.