[esb-issues] [JBoss JIRA] Updated: (JBESB-1918) Implementation of ScriptingAction is inefficient and incomplete

[Kevin Conner (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBESB-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Conner updated JBESB-1918:
--------------------------------

    Fix Version/s: 4.4 CP2
                       (was: 4.2.1 CP4)


> Implementation of ScriptingAction is inefficient and incomplete
> ---------------------------------------------------------------
>
>                 Key: JBESB-1918
>                 URL: https://jira.jboss.org/jira/browse/JBESB-1918
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta
>    Affects Versions: 4.4
>            Reporter: Jiri Pechanec
>             Fix For: 4.4 CP2
>
>
> The ScriptingAction should be polished for beter perfromance and functionality as Groovy scripting action
>  - BSFManager should be created in intialize(), not process() method (credit goes to Kevin :-))
>  - The script reload should be supported
>  - Is it necessary to process BSF config file? Cannot we use getLangFromFilename method?
>  - It should be probably stated in the docs that for compiled scriping languages it is not guranteed that the compliation is done only once which can lead to performance degradation - native action can be preferred in such case
>  - If the laguage is not provided in configuration and script is passed via message, the language has null value when invoking BSF API. This has to be checked and either exception should be thrown with explanantion or the language code should accompany message in body slot or property

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira