Through simple and OGNL we have nice easy ways to read the properties of
beans in the body, headers, or properties. But what I cannot find is an
easy way to invoke a setter on a bean property, but perhaps I am missing
something.
I can certainly create a bean or processor to invoke the setter, but
Yeah, LIKE I SAID, I know I can break out to a bean or a processor, but
that is such a heavyweight solution to do something so simple that really
should be built into Camel. You have to create a class, come up with some
meaningful name of the class, repeat that name a couple of times if using a
Spr
On Tue, Sep 3, 2013 at 5:51 PM, Dale King wrote:
> Through simple and OGNL we have nice easy ways to read the properties of
> beans in the body, headers, or properties. But what I cannot find is an
> easy way to invoke a setter on a bean property, but perhaps I am missing
> something.
>
> I can ce
Hi
The DSL in camel is intended to be as identical between Java and XML
as possible. In fact the XML is generated based on Java classes.
This allows people to easily transition between java and xml dsl. And
also read examples in Java and understand how to do that in XML - and
vice versa etc.
So
Thinking about this some more the real issue is not so much direct support
for setting properties or invoking arbitrary methods because we have things
like OGNL which can do that work for us. For example, the OGNL expression:
request.body.someProperty = request.headers.foo
would do the trick f
Hi
You can use the language component, and set transform=false
http://camel.apache.org/language
Though the idea of having a
On Fri, Sep 20, 2013 at 1:54 AM, Claus Ibsen wrote:
> Hi
>
> You can use the language component, and set transform=false
> http://camel.apache.org/language
>
That seems to do the trick, but having to add ?transform=false is a pain. I
personally would argue that the default for transform should h
