On Thu, Jun 26, 2003 at 05:22:38PM -0700, Craig R. McClanahan wrote: > Accessing Java objects defined in the system class loader doesn't require > anything new -- JNI provides all the necessary hooks. But, to interact > with web app resources, you need to do things like load classes from the > webapp's class loader, and gain access to the ServletContext instance, > and perhaps even do nice things like utilize the servlet container's > session mechanism for scripting languages that don't have such a notion. > Such things can be designed and built for a particular server today, but > there's no standard approach; hence the JSR. >
Hmmm. It's going to be interesting to see the confluence of 223 and 045 (debugging support for other languages); I think the integration of languages via JNI is going to present a near-brick wall when it comes to sane debugging (that said, 045 assumes that compilation to bytecode is possible, which may allow it to preclude some of the languages brought in under 223). But then, what do I know? :) I will say that BSF does provide the object registry for languages that are implemented in Java; it's up to the individual BSFEngine implementation to mediate access to those objects. Having a BSFEngine that "does the right thing" via JNI is not hard to envision (in fact, I think the ActiveScript engine did something similar for WSH). Victor -- Victor J. Orlikowski | The Wall is Down, But the Threat Remains! ================================================================= [EMAIL PROTECTED] | [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
