camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: More data transformation features in Camel
Date Mon, 17 Sep 2012 12:59:24 GMT
On Sun, Sep 16, 2012 at 7:32 PM, Raul Kripalani <> wrote:
> Hi guys,
> A fair number of users rely on Camel for business orchestration, with
> varying degrees of complexity.
> One shortcoming of Camel compared to BPEL is that you can't embed
> assignment and field-focused transformation rules, like you can do with the
> BPEL Assign activity. With XML payloads, I would love to copy, transfer,
> transform values from a source to an origin, without having to write an
> external resource (XSLT, XQuery, Velocity template, etc.). Take a look at
> the data manipulation features in BPEL [1].
> What do you think?
> Also, something that's missing is running transformation scripts contained
> in files. Right now, we can only embed Groovy, JS, JRuby, etc. scripts
> inside Expressions or Predicates. I'd love to be able to create an endpoint
> like: "groovy:file:/opt/resources/transformMessage.groovy", and have Camel
> take care of the appropriate variable bindings to make the Exchange,
> Headers, Properties, Context, etc. available to the script.

This is already supported, see the language component

It can load the script from resources.

And many of the languages have details from the exchange/message/camel
context bound to the script language.
eg as we talk about here

> Does anyone have experience with Spring's support for Dynamic Languages in
> this context? [2]. Maybe having Spring take care of plugging in the script
> so that it's referenceable as a normal bean?
> Regards,
> Raúl.
> ---
> *Raúl Kripalani *
> Enterprise Architect, Program Manager, Open Source Integration specialist
> |
> | twitter: @raulvk
> [1]
> [2]

Claus Ibsen
Twitter: davsclaus, fusenews
Author of Camel in Action:

View raw message