[esb-issues] [JBoss JIRA] Commented: (JBESB-1918) Implementation of ScriptingAction is inefficient and incomplete
[
https://jira.jboss.org/jira/browse/JBESB-1918?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-1918:
-----------------------------------
Kevin and Burr: Sorry I've been on PTO this past week, thus my delayed responses.
Kevin: The other reasons I chose BSF over javax.script:
1. BSF as a library was already available in the underlying AS.
2. Being new to engineering's processes, I didn't know the process of getting new
libraries introduced. (Related: it was a pain just to get BSF - which was already there -
upgraded.)
I very much agree with your "real question that has to be answered" statement.
Honestly I don't know how well supported javax.script is from a provider standpoint.
It would be good to look into, as well as to understand it's precompilation support
(and whether that piece is optional for the providers to implement, and which of them
actually do).
Burr: I left that comment in there such that people would know the current limitations and
not open a slew of bugs just because the languages they thought would work don't, and
why. I can remove it if you think it best, in fact I was going to tweak the docs again
anyway to clear up the BSH confusion. However, maybe we should time it with the ESB
release that will contain the AS release, which in turn contains the BSF upgrade?:
https://jira.jboss.org/jira/browse/JBAS-5249
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 CP1
Attachments: jbossesb-scripting-enhancements.zip, Scripting.odt, Scripting.pdf
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.
--
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