shared/lib driving me crazy! RE: shared/lib seems to be ignored
I've established that no jar files are being loaded from shared/lib. I've
added the -verbose:class switch to catalin.bat and I'm redirecting the
output to a file. I've performed a text search for shared\lib within the
file and found no matches. This is the case for all jar files not just
mine. To make sure it wasn't just my jar file I placed standard jar files
that Struts depends on in shared/lib and they don't get loaded either. The
strange thing is that Tomcat is locking the jars while it's running, but
doesn't load classes from them. Can anyone help me? I'm losing my mind!
-Sean
-Original Message-
From: Duncan, Sean [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 19, 2005 4:47 PM
To: 'tomcat-user@jakarta.apache.org'
Subject: shared/lib seems to be ignored
I've been running into this for a few releases now, but I haven't had time
to resolve it.
I'm developing a suite of web applications that share a common core. For
various reasons it is important that all of the apps within the suite
reference the core from the same classloader. All my reading has directed
me toward placing the core jar file in ${CATALINA_HOME}/shared/lib.
Unfortunately from release 4.1.x all the way up to 5.5.x the jar file seems
to be completely ignored when I place it in ${CATALINA_HOME}/shared/lib. On
the other hand everything works fine when I place it in
${CATALINA_HOME}/common/lib. Do I have to explicitly configure Tomcat to
look in ${CATALINA_HOME}/shared/lib?
Thanks in advance for your time.
-Sean
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: shared/lib driving me crazy! RE: shared/lib seems to be ignor ed
Eureka! I finally found the fix! For some reason our context fragment had
the priviliged attribute set to true. Setting this to false makes
everything work as expected. It is a little confusing given the purpose of
this attribute. My guess is that priviliged contexts have added security
restrictions that probably would have necessitated modifying catalina.policy
(just a shot). If anyone of the extreme gurus on this list has more insight
into this weird behavior I would love to hear it. As far as my immediate
requirements go my apps do not need access to container servlets so setting
priviliged to false works fine.
-Sean
-Original Message-
From: Duncan, Sean [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 20, 2005 10:05 AM
To: 'Tomcat Users List'
Subject: shared/lib driving me crazy! RE: shared/lib seems to be ignored
I've established that no jar files are being loaded from shared/lib. I've
added the -verbose:class switch to catalin.bat and I'm redirecting the
output to a file. I've performed a text search for shared\lib within the
file and found no matches. This is the case for all jar files not just
mine. To make sure it wasn't just my jar file I placed standard jar files
that Struts depends on in shared/lib and they don't get loaded either. The
strange thing is that Tomcat is locking the jars while it's running, but
doesn't load classes from them. Can anyone help me? I'm losing my mind!
-Sean
-Original Message-
From: Duncan, Sean [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 19, 2005 4:47 PM
To: 'tomcat-user@jakarta.apache.org'
Subject: shared/lib seems to be ignored
I've been running into this for a few releases now, but I haven't had time
to resolve it.
I'm developing a suite of web applications that share a common core. For
various reasons it is important that all of the apps within the suite
reference the core from the same classloader. All my reading has directed
me toward placing the core jar file in ${CATALINA_HOME}/shared/lib.
Unfortunately from release 4.1.x all the way up to 5.5.x the jar file seems
to be completely ignored when I place it in ${CATALINA_HOME}/shared/lib. On
the other hand everything works fine when I place it in
${CATALINA_HOME}/common/lib. Do I have to explicitly configure Tomcat to
look in ${CATALINA_HOME}/shared/lib?
Thanks in advance for your time.
-Sean
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 5.5 - path attrubute ignored in context fragments
I'm migrating a suite of applications from 5.0.x to 5.5.x. The path attribute no longer has any effect on the web applications context path. I understand from the documentation that this is by design, but I think it may have been a mistake. Since we deploy a suite of applications to Tomcat our contexts usually take the form /suitename/appname. As far as I can see there is no way to accomplish this without nesting the context entries directly within server.xml (a practice which the documentation discourages and I dread going back to). Can we make the path attribute work again or is there some secret file nameing scheme I can use for the context fragment? Thanks in advance for your time.
