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. 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 http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk [1] http://docs.oracle.com/cd/E11036_01/integrate.1013/b28981/manipdoc.htm [2] http://static.springsource.org/spring/docs/3.0.x/reference/dynamic-language.html
