Serge / Noel I believe that adding JSP style <scriplet> support (which uses BSF) and/or JSP EL would be a powerful addition to James'. But should it be both or just one?
A quick look at the "Expression Language API" in "JavaServer Pages T Specification Version 2.0" suggests that coupling James' Mailet Container to an Expression Language evaluator would be entirely possible and not so "left field" as [Serge] suggested. James would be leveraging any Expression Language implementation (interfaces defined in the javax.servlet.jsp.el package), such as the pre-release Apache Commons component or the one in Sun's J2EE SDK 1.4 Beta 2. It could work very well and has some advantages over <scriptlet>s/BSF. Its cleaner and will better promote a community of mailets/matchers as there is a single scripting language. (And yes, I did say earlier that an advantage of BSF is that it doen't impose a sole scripting langauge :) Unfortunately EL is not really here yet, while BSF is. If the timeframe for adding scripting support is less than 3 months, EL is probably a no go. If the timeframe is longer then my opinion (for what it's worth) is that if little or no work has been done on BSF, focussing efforts on EL may be the better option. The third way is to support both, implementing <scriptlet>s/BSF now with EL coming later. If its known that EL is coming, any work refactoring to support the BSF API can also take into account the needs of the EL API. I'ld be interested to hear your take on this and happy to take on some of the work of putting together a specification based on everyones views (if I'm neither stealing work or duplicating effort). -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
