I'm no expert, but could the use of propertyPlaceholder
http://camel.apache.org/using-propertyplaceholder.html help achieve
similar results (define the FTP details once) and use many??
--
View this message in context:
http://camel.465427.n5.nabble.com/FTP-Component-configuration
this message in context:
http://camel.465427.n5.nabble.com/FTP-Component-configuration-tp5759497p5759584.html
Sent from the Camel - Users mailing list archive at Nabble.com.
to achieve the same effect.
Thanks again.
Best regards,
Atanas
--
View this message in context:
http://camel.465427.n5.nabble.com/FTP-Component-configuration-tp5759497p5759584.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
Red Hat, Inc
:
http://camel.465427.n5.nabble.com/FTP-Component-configuration-tp5759497p5759590.html
Sent from the Camel - Users mailing list archive at Nabble.com.
the configuration once on the component level - connection factory, JNDI
configurations if necessary, etc., and have it reused by each endpoint
instance create with the component.
--
View this message in context:
http://camel.465427.n5.nabble.com/FTP-Component-configuration-tp5759497p5759590.html
Sent
), 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
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
