[jboss-dev-forums] [Design of JBoss ESB] - Re: Scripting Language ESB Action

In terms of what we use under the hood, I think we'd obviously like to hide that re what people see in the action configs. So internally, we could support scripting languages X, Y and Z via JSR-223 if they are JSR-223 compliant. For non compliant scripting engines, we'd need to support those by hand. In terms of usage, we could infer the engine from the script extension (.groovy, .php etc), only using the "scriptEngine" property as an override. Could also make action scripts more of a first class construct ala: | <action script="MyGroovyScript.groovy" name="My Blah" /> | (note the action defines a "script" instead of a "class"). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4018741#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...