Re: parameter types in RouteTemplateDefinition

2021-02-01 Thread Jörg Jansen
Hi Claus, thanks, your provided solution seems to work fine for me :-) Thank, Joerg Am Mo., 1. Feb. 2021 um 14:20 Uhr schrieb Claus Ibsen : > > Hi > > Making it nicer with errorHandler(ref) in the next release > https://issues.apache.org/jira/browse/CAMEL-16126 > > On Mon, Feb 1, 2021 at 2:09

Re: parameter types in RouteTemplateDefinition

2021-02-01 Thread Claus Ibsen
Hi Making it nicer with errorHandler(ref) in the next release https://issues.apache.org/jira/browse/CAMEL-16126 On Mon, Feb 1, 2021 at 2:09 PM Claus Ibsen wrote: > > Hi Jorg > > Yeah that is a good question. At first route templates is designed to > be simple from the beginning. > > Can you try

Re: parameter types in RouteTemplateDefinition

2021-02-01 Thread Claus Ibsen
Hi Jorg Yeah that is a good question. At first route templates is designed to be simple from the beginning. Can you try with errorHandler(new ErrorHandlerBuilderRef("{{my-error-handler-ref}}")); On Mon, Feb 1, 2021 at 11:48 AM Jörg Jansen wrote: > > Hi Claus, > > thanks for your response. >

Re: parameter types in RouteTemplateDefinition

2021-02-01 Thread Jörg Jansen
Hi Claus, thanks for your response. I agree, just to use String literals. But maybe you can tell me what's the best way to add a route-specific errorhandler? I solved my issue by doing it the following way: ModelCamelContext modelCamelContext = camelContext.adapt(ModelCamelContext.class);

Re: parameter types in RouteTemplateDefinition

2021-01-31 Thread Claus Ibsen
Hi The template parameters are intended as text based placeholders,eg for string, numbers, booleans, etc. If you need to pass in objects, then it should be as reference to objects to use in the registry via their bean id. On Tue, Jan 26, 2021 at 9:20 PM Jörg Jansen wrote: > > Hi all, > > I’ve

parameter types in RouteTemplateDefinition

2021-01-26 Thread Jörg Jansen
Hi all, I’ve a Question About the usage of Route templates (Camel-3.7.0). As far as I see, it is possible to provide every kind of object as a paramter. But within the template, it seems to me, that those Parameters are only processed as Strings. So my question: Is there a way/best practice to