Howdy, What Steve said is right on target. Your patch is not likely to make it into the tomcat code base ;)
A couple of other pointers, however: - Patches are always welcome -- so thanks for contributing ;) - Don't attach them to messages: open a bugzilla enhancement request and attach your patch, or better yet, a diff file from current sources to your patch, in the bugzilla issue. - You may wish to discuss the need for and intent of your patch on the dev list before writing the patch itself. - If you intend to contribute more, which I hope is the case, please read the guidelines for getting involved with jakarta: http://jakarta.apache.org/site/getinvolved.html Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Sent: Tuesday, October 28, 2003 7:19 AM >To: Tomcat Users List >Subject: Re: Needed more support for catalina.base in Bootstrap > >> From: Rodrigo Ruiz <[EMAIL PROTECTED]> > >> Recently I have been trying to install and configure an OGSA server >> (www.globus.org) deployed over a Tomcat container. The problem I have is >> that it requires a lot of Tomcat customization: additional connectors in >the >> server.conf, additional jars in the common/lib, common/endorsed and >> server/lib directories, conf/web.xml modifications, and so. >> >> In order to keep track of these changes, I decided to use a shared Tomcat >> installation, and do all the dirty business in a separated Tomcat >instance, >> pointing CATALINA_BASE to it. Doing this I noticed that there was no >place >> for putting my common/lib and server/lib jars. > >This sounds backwards. When using separate CATALINA_HOME and >CATALINA_BASE locations, > >CATALINA_HOME - > > the "central" location. Classes used by tomcat (server and common > respositories) are taken from this location. You'll also use the bin > directory for this location. > >CATALINA_BASE - > > the "lightweight" installations. These contain web applications, > their own logs, own configuration files, and make use of their own > "shared" class repositories. If you think about it, this makes > sense: separate CATALINA_BASEs can have different web applications, > so the set of web application library depencies can vary from one > CATALINA_BASE to the next. > > >> Digging in the source code, I found that CATALINA_BASE is not used at all >> when building the common and catalina class loaders. > >That's correct. CATALINA_BASE uses the shared class loader, and >CATALINA_HOME uses common and server. > >-- >Steve > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
