gt;
> Is that a known limitation?
>
Yes its a limitation currently. I have logged a JIRA
https://issues.apache.org/jira/browse/CAMEL-5252
> --
> Gavin Scott
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Invoking-a-bean-returned-by-a-previous-bean-i
.String to the required
> type: org.apache.camel.language.simple.SimpleTest.Animal with value donkey
>
> Is that a known limitation?
>
> --
> Gavin Scott
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Invoking-a-bean-returned-by-a-previous-bean-invocation-tp5676696p5684000.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
java.lang.String to the required
type: org.apache.camel.language.simple.SimpleTest.Animal with value donkey
Is that a known limitation?
--
Gavin Scott
--
View this message in context:
http://camel.465427.n5.nabble.com/Invoking-a-bean-returned-by-a-previous-bean-invocation-tp5676696p5684000.html
Sent from the Camel - Users mailing list archive at Nabble.com.
exchange.getIn().setBody("Camel");
exchange.getIn().setHeader("max", 4);
exchange.getIn().setHeader("min", 2);
assertExpression("${body.substring(${header.min},
${header.max})}", "me");
}
>
> --
> View this me
Thank you for your reply.
Does the simple language also allows us to send multiple method parameters
like the new features offered in the bean binding?
--
View this message in context:
http://camel.465427.n5.nabble.com/Invoking-a-bean-returned-by-a-previous-bean-invocation-tp5676696p5678641
t;
> class MyBean {
> MyReturnedBean getBean () {
> return new MyReturnedBean();
> }
> }
>
> class MyReturnedBean {
> void doSomething() {
> }
> }
>
> I really appreciate your help.
>
> --
> View this message in context:
> http://cam
class MyBean {
MyReturnedBean getBean () {
return new MyReturnedBean();
}
}
class MyReturnedBean {
void doSomething() {
}
}
I really appreciate your help.
--
View this message in context:
http://camel.465427.n5.nabble.com/Invoking-a-bean-returned-by-a-previous-
