If this is the only java scripting functionality that is required for acs 4.0, then it would be relatively easy to implement in nsjava. I have however been lately working on merging nsjava and tclblend together, which would give complete access to the java api from tcl. I think that most of the tclblend tcl api commands could be made to work in nsjava/aolserver. The following is a list of the tclblend tcl api:
tcl command | description |
java::new : | Allocate Java objects. |
java::call : | Invoke static Java methods. |
java::field : | Get and set Java field values. |
java::instanceof : | Determine if an object is an instance of a Class. |
java::prop : | Manipulate Java Bean properties. |
java::bind : | Bind a Tcl script to a Java event. |
java::event : | Query event objects in a Java event callback. |
java::info : | Introspect Java objects and classes. |
java::null : | Get a handle to the null Java reference. |
java::isnull : | Test a handle to see if refers to null. |
java::lock : | Lock a Java object so that it can not be garbage collected. |
java::unlock : | Unlock a Java object that had been locked previously. |
java::autolock : | Manage automatic locking of Java references during interactive sessions. |
java::load : | Load a Tcl extension defined in a Java class. |
java::defineclass : | Convert binary .class data into a java.lang.Class object. |
java::getinterp : | Get a handle to the tcl.lang.Interp object. |
java::throw : | Throw a Java exception. |
java::try : | Catch a Java exception. |
java::cast : | Cast a Java object from one type to another. |
java::import : | Import a Java class name so that fully qualified name need not be used. |
javaObj : | Invoke instance methods on an object. |
javaArrayObj : | Invoke methods on an array object. |
nsjava already supports the equivalent of the tclblend java::call command and what Ben has proposed corresponds to the tclblend java::new and the javaObj api calls.
I still have quite a bit of work on the tclblend/nsjava merge, and I don't think that it would be practical for me to finish the work in time for the acs 4.0 porting effort. I would however like people who are looking at the new acs 4.0 code to let me know if they see instances in the code where it would be necessary to add code to nsjava to support additional java api functionality that corresponds to what I have illustrated with the tclblend api description.