Jasper does not use it and I really don't think using BSF in this role (as a way to script enable JSPs) is the 'right thing to do'. First major problem is abysmal performance. Second major problem is with debugging. The second problem can probably be solved(?). I don't see how the first problem can be solved.
Bill
Oh, one more thing pops to mind... use of scripting languages from the Java environment of JSP is rather unnatural. Passing script variables back and forth between java and the scripting language environment is messy and needs some hacks to jasper. Chuck or Victor should be able to provide more detail.
a) ad "usage of scripting languages in the context of JSP is rather unnatural": why *unnatural*, for God's sake? I see the contrary to be true, opening up JSPs to solving problems in non-Java languages as well, *if* fitting. As important as Java is, there are applications/problems where non-Java-languages may be preferable, e.g. from scripting to interpreting dynamically created statements.
[BTW, Microsoft allows to use *any* scripting language for their ASP, ie. the JSP counterpart on Windows: they support any WSH-scripting language out of the box.]
b) ad "abysmal performance": could you elaborate, please? Have not seen *any* *abysmal* performance yet. What applications are you talking about and what languages, and what do you judge to be "abysmal performance"??
What are you using/employing BSF for?
Regards,
---rony
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
