What about including scripting support in trunk?
What are your preferences between the Guillermo BeanShell solution and
the previous BSF one?
Should we instead include both of them?
I think it would be cool to have this things bundled by default so users
could start sharing simple scripts they use for specific tasks and many
specific configurations now available only via custom mailets could be
solved via custom-config.xml scripts.
I did a few searches but I cannot find the sources for the
ScriptedMailet/ScriptedMatcher classes from Steve Brewin.
Does anyone got this sources?
I'd like to have a JIRA issue created with such code so we can review
the source code and have much more informations on what to do.
AFAIK Beanshell is supported by BSF so if we could add script
externalization/reloading to the BSF mailets we would have the best of
both worlds.
Stefano
Guillermo Grandes (JIRA) wrote:
[ http://issues.apache.org/jira/browse/JAMES-599?page=comments#action_12431286 ]
Guillermo Grandes commented on JAMES-599:
-----------------------------------------
Well, seeing two versions and comments of Steve Brewin...
Two versions compared + (positive) vs - (negative)
ScriptedBeanShell
+ 70 lines of source code for Mailet / Matcher
+ Scripts in separated files
+ Don't need restart James for reload changes of scripts
- Don't have mutli languaje scripting
+ BeanShell is true Java (JSR-274)
+ KISS principle,... Keep It Simple, Sweetheart! :-)
ScriptedBSF (IBM Bean Scripting Framework)
- 500 lines of source code for Mailet / Matcher
- Scripts inline (SAR-INF/config.xml)
- Need restart James for reload chanages of config.xml
+ Mutli languaje scripting
+ BML, JScript (only win), Mozilla Rhino, NetRexx, PerlScript, VBScript, Jacl,
JPython, LotusXSL
? Complex / Featured
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
