camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CAMEL-3964) Script arguments
Date Sun, 29 May 2011 08:38:47 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen reassigned CAMEL-3964:
----------------------------------

    Assignee: Claus Ibsen

> Script arguments
> ----------------
>
>                 Key: CAMEL-3964
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3964
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-script
>    Affects Versions: 2.7.1
>            Reporter: Teiva Harsanyi
>            Assignee: Claus Ibsen
>            Priority: Minor
>              Labels: camel-script, jsr-223, script, scripting
>             Fix For: 2.8.0
>
>         Attachments: patch.txt
>
>
> As I said here : http://fusesource.com/forums/thread.jspa?threadID=2946&tstart=0,
the ScriptEngine class (http://download.oracle.com/javase/6/docs/api/javax/script/ScriptEngine.html)
provides a put method which enable to add a Java object into the created script, thanks to
the JSR-223. But Camel does not provide a "bridge" to this method.
> So I propose to pass the arguments via the header map of the message.
> Indeed, on client side, I created a Map<String, Object> which contains the future
scripts arguments. Then I put this map into the header.
> Next on the camel-script component, I check a particular key (a public static final attribute
that I added) and if the value returned is a Map, I try to add the Map's objects with the
engine.put(String, Object) method.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message