Thx, that’s what I suspected!
M
> On 23 Apr 2020, at 11:26, Guillaume Nodet <gno...@apache.org> wrote:
>
> Le jeu. 23 avr. 2020 à 10:06, Mikael Andersson Wigander <
> mikael.grevs...@gmail.com> a écrit :
>
>> Hi
>>
>> How can I combine the endpoint DSL with dynamic property definitions such
>> as:
>>
>
> You can use property placeholders with the endpoint DSL, but the goal of
> the
> dsl is to provide some type safety for properties. In order to do that,
> you need to
> know the endpoint type beforehand. Soin your use case where the component
> is not know, you can't leverage the endpoint dsl much.
>
>
>>
>> final String toStr = "{{shuttle.ftp.outgoing.url}}" +
>> "&username={{shuttle.ftp.username}}" +
>> "&password={{shuttle.ftp.password}}" +
>> "&allowNullBody=false" +
>> "&consumer.bridgeErrorHandler=true" +
>> "&throwExceptionOnConnectFailed=true" +
>> "&pollStrategy=#defaultPollStrategy";
>>
>> from("{{shuttle.outgoing.transactions}}")
>> .routeId("Sending-SHUTTLE-FTP")
>> .autoStartup("{{shuttle.ftp.outgoing.startup}}")
>> .wireTap("seda:ping")
>> .to(toStr)
>> .log("XML file(s) sent")
>> .end();
>>
>>
>> What I’d like is to have the option to have our DEV environment setup
>> using say FTP but in INTEGRATION and PROD it will be SFTP. Since the
>> endpointDSL is somewhat “hardcoding” the endpoint I don’t really know how
>> to do it
>>
>> Thx
>>
>> M
>
>
>
> --
> ------------------------
> Guillaume Nodet
