You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/07/11 10:44:04 UTC
[jira] [Commented] (CAMEL-6098) Add script to the DSL to invoke a
expression language and allow noop changes on the Exchange
[ https://issues.apache.org/jira/browse/CAMEL-6098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623312#comment-14623312 ]
Claus Ibsen commented on CAMEL-6098:
------------------------------------
We should allow to load the script from classpath, so you can do
{code}
<script>
<groovy>resource:classpath:com/foo/cool.groovy</groovy>
</script>
{code}
> Add script to the DSL to invoke a expression language and allow noop changes on the Exchange
> --------------------------------------------------------------------------------------------
>
> Key: CAMEL-6098
> URL: https://issues.apache.org/jira/browse/CAMEL-6098
> Project: Camel
> Issue Type: New Feature
> Components: camel-core, eip
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.16.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Changing-POJO-attribute-from-the-body-using-the-Simple-Expression-Language-tp5727971.html
> We should have a script in the DSL
> {code:xml}
> <route>
> ...
> <script>
> <groovy>some groovy stuff here</groovy>
> </script>
> ...
> </script>
> {code}
> The script is then invoked and allows noop to avoid changing the message body.
> Currently you can only do
> {code:xml}
> <transform>
> <groovy> ... </groovy>
> </transform>
> {code}
> ... and that may change the message body with the return value from groovy.
> With <script> you can avoid this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)