However, when running under a single Tomcat instance, I think
that there is only 1 process (only one JVM in use). There may be several
threads, but only one process is in use. Therefore, there is only 1 data
segment that can be used.
Or am I completely off base?
No, you are right, 1
]' [EMAIL PROTECTED]
Date: Friday, June 01, 2001 11:18 AM
Subject: RE: Classloader, JNI and already loaded in another classloader
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
Just to give a thought for your situation, how would you think if we
place a plain java bean(i.e., common wrapper class) that interact with the
c++/dll module and provide the access from the Web components, i.e.,
servlet/jsp --- the jb's user --- to the java bean(jb). In that case,
multiple jb's
[...]
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++
, 2001 10:30 AM
To: [EMAIL PROTECTED]
Subject: Re: Classloader, JNI and already loaded in another classloader
Just to give a thought for your situation, how would you think if we
place a plain java bean(i.e., common wrapper class) that interact with the
c++/dll module and provide the access from
]
Date: Friday, June 01, 2001 11:18 AM
Subject: RE: Classloader, JNI and already loaded in another classloader
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
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
