You can place common library in common/lib. If that class needs to use
reflection to instantiate any classes in your webapp - it may fail. (But
since this looks to be a standalone utility - that doesn't seem to be the case)
In the case of the reloads - a dll may only be registered once during the
life of the JVM. SO you might need a utility class at the common/lib (or
common/classes) level to handle the registration of that class so that it
only happens once.
-Tim
John MccLain wrote:
we currently have 1 project in tomcat webapps dir. We want to add another
project there. The problemn is that we would like to have both projects'
web-inf/lib populated with the same set of libraries (jar files). When we
kick off Tomcat with this configuration,The second context fails to load
because as part of context initialization in both apps, we are using JST.dll
and .jar - A Registry reading utility; It seems that if context1 loads a
.dll, it cannot be reloaded for context2. We are getting "Native Library
C:\tomcat\webapps\Acuity\Configuration\jst.dll already loaded in another
classloader"
How can we avoid this?
If we place the .dll and .jar in Tomcat/common/lib, and set our System path
to it, will this solve the problem?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
