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

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 Assignee: Mark Little 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 language is not recognized (not in Map) during initialization an exception should be thrown. Currently it is supposed that the file extension is language name, which is probably unintentional, and could lead to exception while processing the first message.