Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.223.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1416679980179-5759497.post@n5.nabble.com>
References: <1416679980179-5759497.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Mon, 24 Nov 2014 12:46:34 +0100
Message-ID: 
 <CAGB5yNkeg5DwCVufBv1x9+eD8Xw8sX8BgdXEGxr6HnbXs9tj1A@mail.gmail.com>
Subject: Re: FTP Component configuration
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: text/plain; charset=UTF-8

Hi

No you cannot do that, you need to set the host/port etc in the uri,
when you define the endpoint as an uri string.


On Sat, Nov 22, 2014 at 7:13 PM, Atanas Shindov
<atanas.shindov@gmail.com> wrote:
> Hi guys,
>
> After I've watched the  Riding Camel
> <https://skillsmatter.com/skillscasts/2450-riding-camel>   presentation by
> James Strachan I tried to implement a route where all endpoints are FTP
> based, but instead of configuring each FTP endpoint with hostname, port, and
> login credentials, I wanted to configure all this just once on a
> FtpComponent and have all these configurations automatically applied to all
> my endpoints created with this component. I imagined that Camel would allow
> me to do something like this:
>
> FtpComponentConfiguration config = new FtpComponentConfiguration();
> config.setHostname("localhost");
> config.setPort("21");
> config.setUsername("user");
> config.setPassword("password");
> FtpComponent ftp = new FtpComponent(config);
>
> context.addComponent("myFtp", ftp);
>
> And then my route's DSL would look like this:
>
> from(myFtp://directory/fromDirectory).to(myFtp://directory/toDirectory);
>
> However, it looks like that Camel's FTP component can't be used like this
> (or at least I can't find a way to do it) which is very strange considering
> the fact that James used namely FTP as an example to explain the idea behind
> the components. I've used this approach for JMS - you configure a JMS
> component just once with that's necessary (e.g. connection factory), and
> then refer it in each JMS endpoint.
>
> Am I missing something or the current implementation of FTP does not allow
> this?
>
> Best regards,
> Atanas
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/FTP-Component-configuration-tp5759497.html
> Sent from the Camel - Users mailing list archive at Nabble.com.


-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/