[jboss-jira] [JBoss JIRA] Commented: (JBESB-445) Custom Action:Scripting
Tom Fennelly (JIRA)
jira-events at lists.jboss.org
Tue Feb 27 06:35:35 EST 2007
[ http://jira.jboss.com/jira/browse/JBESB-445?page=comments#action_12354416 ]
Tom Fennelly commented on JBESB-445:
------------------------------------
Ah OK.
Wouldn't it be useful to inject the properties/ConfigTree into the script (as well as the message). This way you can parameterize the scripts from the config.
I wonder how this action will perform? I'd imagine that creating a new instance of it every time will be a bit of a dog. But I suppose this is an issue we have with all our actions - they're non-singleton.
I'd suggest that if/when we make the actions (or whatever they'll be called in the new architecture) singleton (by default), we could look at using the GroovyClassloader and require the Groovy scripts to implement our ActionProcessor interface (or whatever we call that). Then we can just treat Groovy scripts like any other java class (plus cache the instance on a per action basis).
> Custom Action:Scripting
> -----------------------
>
> Key: JBESB-445
> URL: http://jira.jboss.com/jira/browse/JBESB-445
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Rosetta
> Affects Versions: 4.0 Maintenance Pack 1
> Reporter: Burr Sutter
> Assigned To: Mark Little
> Priority: Optional
> Fix For: 4.0 Maintenance Pack 1
>
> Attachments: groovy_action.zip
>
>
> Provide an out-of-the-box action that allows for the integration of scripting languages for as ESB actions. An example of a scripting language would be Groovy or Beanshell. A quickstart example should also be created to illustrate the capabilities.
> Gregory Pierce provided a quickstart for Groovy.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list