user respectively.
Agreeable?
If so, isn't java bean as a user calling the DLL twice create the same
scenario?
So two different accesses from the jb's user can get the separate data
returned
by the DLL.
Pae
-Original Message-
From: Mark Benzel [EMAIL PROTECTED]
To: '[EMAIL PROTECTED
I have a webapp running under Tomcat 3.2.1 that needs to make JNI calls in
order to access data and methods in legacy C++ code. A servlet is loaded on
startup of the webapp that, as part if its init method, causes a data set
specific to that webapp instance to be loaded into the C++ data
Yes, it makes sense. However, I'm not sure if it solves my problem. In
the scenario you describe, I would want to have 2 Java Beans, each accessing
a separate instance of the C++/DLL. That's because the data contained in
the
C++/DLL used by webapps/aaa is different than the data contained in
I'll give it try. Thanks.
-Original Message-
From: Bo Xu [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 01, 2001 10:56 AM
To: [EMAIL PROTECTED]
Subject: Re: Classloader, JNI and already loaded in another
classloader
[...]
I have a webapp running under Tomcat 3.2.1 that needs to make
