Re: Camel bean 4.8.1 toD uri issue

2025-02-11 Thread Claus Ibsen
Hi What you do with is correct. You specify the method signature that Camel should call. The bean component is able to adapt to this. Using toD is not needed and it has a different purpose here. The will calculate a literal uri string ahead of time. This means the simple expression values are a

Re: Camel bean 4.8.1 toD uri issue

2025-02-09 Thread logesh
In that case are we isolating just to string based methods for toD and custom wont me supported? On Mon, Feb 10, 2025, 1:05 PM Claus Ibsen wrote: > Hi > > This is as designed when you use toD then you use the simple language that > are literal/string based. > Avoid all the method overload compl

Re: Camel bean 4.8.1 toD uri issue

2025-02-09 Thread Claus Ibsen
Hi This is as designed when you use toD then you use the simple language that are literal/string based. Avoid all the method overload complexity and just use a new method name. On Mon, Feb 10, 2025 at 8:08 AM logesh wrote: > Hi, > > We have another issue with camel bean and methid invocation

Re: Camel bean 4.8.1 toD uri issue

2025-02-09 Thread logesh
Hi, We have another issue with camel bean and methid invocation but this time its on the bean menthod invocation thats done thru toD uri. Calling a bean method using the below snippet works when access the header stored properties .the property1 in headers gets resolved to the custom class type