"W. John Guineau" wrote:
> Well, if I use the Java package, then the Tcl code would not have access to
> the same run-time instance of the JVM that our code is running in, right?
I don't see why not. There is only one JVM per process anyway. (That
is a limitation of the Sun JVM.) I'm not familiar with the code, but by
executing AttachThread the Tcl interpreter can easily get a handle to
the existing JNI environment.
> (starting our Java code from Tcl is, unfortunetly, not an option.)
Understood. I am doing what you describe, except I haven't attempted to
single-step the interpreter and I'm currently using Jacl, not TclBlend.
I have a Java servlet that creates a pool of interpreters, each running
in its own thread. Each interpreter uses the java package and calls
back to Java methods. I haven't yet needed to write any custom
commands, the java package is a "swiss army knife" that way.
--
Jeff Sturm
[EMAIL PROTECTED]
----------------------------------------------------------------
The TclJava mailing list is sponsored by Scriptics Corporation.
To subscribe: send mail to [EMAIL PROTECTED]
with the word SUBSCRIBE as the subject.
To unsubscribe: send mail to [EMAIL PROTECTED]
with the word UNSUBSCRIBE as the subject.
To send to the list, send email to '[EMAIL PROTECTED]'.
An archive is available at http://www.mail-archive.com/tcljava@scriptics.com
