What do you think Jelly's policy should be for mucking around with/modifying the ClassLoader availabel via context? Should I build my own and swap Jellys with it to load the new Classes or is it ok to do the security manipulation on the current classloader like I've done?

-Mark


James Strachan wrote:

From: "Mark R. Diggory" <[EMAIL PROTECTED]>

I'm interested in the possibility that the BSF Taglibrary code could be
reused to do this. Possibly through use of the ExpressionFactory and
manipulation of the ObjectRegistry used. Maybe by providing a means of
switching form the JellyContextRegistry to a ObjectRegistry native to
BSF. The BSF taglibrary code could be reused in the <body> tag to attain
use of BSF scripting in the generated class that is "context
independent" of Jelly while reusing the Expression/ExpressionFactory
code already implemented to easily provide the scripting support. It
might be even possible to provide the ability to reuse BeanShell as
scripting environment via this methodology as well.

Agreed. The Expression interface used inside Jelly is normally reserved for
simple expressions which return values. So a subset of scripting languages.
It'd be cool to add this kind of feature (compiling expressions) into BSF -
right now BSF just has an eval method where you pass in the expression text.

For now what you could do is just get the textual content of a <script> tag
then use the BSF to turn it into Java code.

James
-------
http://radio.weblogs.com/0112098/

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to