Well BeanShell or whatever is fine so far as scripting but no matter what we cannot avoid "bindings". Meaning supplying WHAT objects should be managed. JSR-223 seems not perscriptive so far as the scripting langauge. I'm not against that, but we should have something preferred. I originally kind of favored JavaScript figuring it was a more commodity skill than is Java itself. However, BeanShell is close enough.
An objective ought to be non-java programmers. Something that makes it easy for that group is good. A secondary objective ought to be "protection" meaning you ought not be able to change things through the scripting system that will destabilize the system (although they may produce undesirable mail-routing behavior). Anyhow start thinking about how it would work and what is required to make it work. I'm less interested in "pick-a-standard" than the overall design of the thing and how it affects things like the Mail object. (meaning what needs to change). How should these be loaded? I kind of lean towards a custom deployer....etc View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3868099#3868099 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3868099 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
