tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15774] New: - tomcat5 shared/lib behavior different than that of tomcat4.1.x
Date Fri, 03 Jan 2003 06:50:06 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15774>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15774

tomcat5 shared/lib behavior different than that of tomcat4.1.x

           Summary: tomcat5 shared/lib behavior different than that of
                    tomcat4.1.x
           Product: Tomcat 5
           Version: Nightly Build
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: hoju@visi.com


Using Tomcat-4.1.x, I can have separate instances of Tomcat running which access
their own shared/lib folder.  In Tomcat-5.0 latest nightly build, that doesn't
seem to be the case.  In fact, Tomcat5 only ever sees CATALINA_HOME/shared/lib
where Tomcat4.1.x only ever sees CATALINA_BASE/shared/lib and only when
CATALINA_BASE happens to be the same as CATALINA_HOME does Tomcat4.1.x see
CATALINA_HOME/shared/lib.

For instance, using Tomcat-4.1.18, if I have some jars in
CATALINA_HOME/shared/lib and I start up a new tomcat instance with CATALINA_BASE
set as something other than CATALINA_HOME, the jars in CATALINA_HOME/shared/lib
will *not* be loaded.  Instead, jars will be loaded from
CATALINA_BASE/shared/lib (if it exists).  This is the behavior I expect and love!

However, using Tomcat-5.0, if I set things up the same way, jars in
CATALNIA_HOME/shared/lib *will* be loaded and jars in CATALNIA_BASE/shared/lib
are completely ignored. This is behavior that I don't expect and don't like.

For a concrete example...
I use the capability of running separate instances of Tomcat to run apps which
require different versions of xerces.  I put xerces-1.4.4.jar in
CATALINA_HOME/shared/lib for apps which I use most often.  However, I have other
apps that need either slightly modified version of xerces-1.4.4 or require
xerces-2.x.x.  For those cases, I run separate instances of Tomcat (running on
different ports, of course), each with a distinct CATALNIA_BASE and a local
CATALINA_BASE/shared/lib with the appropriately versioned jars that I need for a
particular set of apps.  Everyone is happy because everyone gets to use their
own shared set of libraries without stepping on each other.

So, obviously, this is a great feature in Tomcat-4.1.x (and, I assume,
Tomcat-4.0.x) but it seems to be broken in Tomcat-5.0.  

Is this new behavior in Tomcat-5.0 a bug or was it intentional?  If it was
intentional, can someone please explain the reasons for the change in behavior
to that of Tomcat-4.1.x?

Jake

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message