RE: NEW_LOADER in m1 tomcat.sh
True the readme is false, I'll correct it ASAP. Si la fortune vient en dormant, ça n'empêche pas les emmerdements de venir au réveil. -- Pierre Dac >-Original Message- >From: Peter B. West [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, March 20, 2001 7:49 AM >To: [EMAIL PROTECTED] >Subject: Re: NEW_LOADER in m1 tomcat.sh > > >The README files in the lib, lib/common and lib/shared directories are >ambiguous. They certainly give the impression that lib still has the >same function as lib/common, there is no lib/container directory, and >lib/README is downright confusing. A bit of m2 seems to have >crept into >the descriptions. Does it mean to say: > >Tomcat uses a hierarchy of class loaders: > > /lib > JARSs (and classes ?) visible > loaded by ??? > >/container /common /apps > (is this /apps or >/shared?) >JARs (and classes?) JARs (and classes?) JARs (etc) >visible only to visible to both the visible only to >tomcat (the container (tomcat) &webapps >container) webapps > >Can someone who knows fill in the blanks and put the modified >version in >lib/README? > >A side question: Is it generally desirable to include lines like > ># The following line prohibits users from directly accessing META-INF ># > >AllowOverride None >deny from all > > >in the description of contexts in mod_jk.conf? > >Peter > > >GOMEZ Henri wrote: >> >> >Can someone please tell me more about this change in >the tomcat.sh >> >startup script? It looks like jars in TOMCAT_HOME/lib are no longer >> >geting added to the classpath- is this the new model? In my project >> >I like to deploy the jars directly to TOMCAT_HOME/lib where >> >they will be >> >found when Tomcat starts up. If someone knows what I should do >> >under the >> >"NEW_LOADER" approach let me know. >> >> The new loader schema split the jar in 3 categories : >> >> 1) container only (ie only used by tomcat) TOMCAT_HOME/lib/container >> 2) application only (only needed by webapps) TOMCAT_HOME/lib/apps >> 3) common (used by webapps and tomcat) TOMCAT_HOME/lib/common > >-- >Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest >"Lord, to whom shall we go?" >
Re: NEW_LOADER in m1 tomcat.sh
The README files in the lib, lib/common and lib/shared directories are ambiguous. They certainly give the impression that lib still has the same function as lib/common, there is no lib/container directory, and lib/README is downright confusing. A bit of m2 seems to have crept into the descriptions. Does it mean to say: Tomcat uses a hierarchy of class loaders: /lib JARSs (and classes ?) visible loaded by ??? /container /common /apps (is this /apps or /shared?) JARs (and classes?) JARs (and classes?) JARs (etc) visible only to visible to both the visible only to tomcat (the container (tomcat) &webapps container) webapps Can someone who knows fill in the blanks and put the modified version in lib/README? A side question: Is it generally desirable to include lines like # The following line prohibits users from directly accessing META-INF # AllowOverride None deny from all in the description of contexts in mod_jk.conf? Peter GOMEZ Henri wrote: > > >Can someone please tell me more about this change in the tomcat.sh > >startup script? It looks like jars in TOMCAT_HOME/lib are no longer > >geting added to the classpath- is this the new model? In my project > >I like to deploy the jars directly to TOMCAT_HOME/lib where > >they will be > >found when Tomcat starts up. If someone knows what I should do > >under the > >"NEW_LOADER" approach let me know. > > The new loader schema split the jar in 3 categories : > > 1) container only (ie only used by tomcat) TOMCAT_HOME/lib/container > 2) application only (only needed by webapps) TOMCAT_HOME/lib/apps > 3) common (used by webapps and tomcat) TOMCAT_HOME/lib/common -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest "Lord, to whom shall we go?"
RE: NEW_LOADER in m1 tomcat.sh
Just put the jar in lib/common :-) Si la fortune vient en dormant, ça n'empêche pas les emmerdements de venir au réveil. -- Pierre Dac >-Original Message- >From: fakhar [mailto:[EMAIL PROTECTED]] >Sent: Monday, March 19, 2001 12:50 PM >To: [EMAIL PROTECTED] >Subject: Re: NEW_LOADER in m1 tomcat.sh > > >Hello > >Could u please guide me that how I configure it. >Thanks >Fakhar >- Original Message - >From: GOMEZ Henri <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Monday, March 19, 2001 2:44 PM >Subject: RE: NEW_LOADER in m1 tomcat.sh > > >> >OK, I just saw the docs on this in m2- however, it >looks like the >> >tomcat.sh needs a few extra lines to load jars from lib/common and >> >lib/container >> >> The load is done in java code at startup :: >> >
Re: NEW_LOADER in m1 tomcat.sh
Hello Could u please guide me that how I configure it. Thanks Fakhar - Original Message - From: GOMEZ Henri <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 19, 2001 2:44 PM Subject: RE: NEW_LOADER in m1 tomcat.sh > >OK, I just saw the docs on this in m2- however, it looks like the > >tomcat.sh needs a few extra lines to load jars from lib/common and > >lib/container > > The load is done in java code at startup :: >
RE: NEW_LOADER in m1 tomcat.sh
>OK, I just saw the docs on this in m2- however, it looks like the >tomcat.sh needs a few extra lines to load jars from lib/common and >lib/container The load is done in java code at startup ::
Re: NEW_LOADER in m1 tomcat.sh
OK, I just saw the docs on this in m2- however, it looks like the tomcat.sh needs a few extra lines to load jars from lib/common and lib/container Thanks, Jason GOMEZ Henri wrote: > >Can someone please tell me more about this change in the tomcat.sh > >startup script? It looks like jars in TOMCAT_HOME/lib are no longer > >geting added to the classpath- is this the new model? In my project > >I like to deploy the jars directly to TOMCAT_HOME/lib where > >they will be > >found when Tomcat starts up. If someone knows what I should do > >under the > >"NEW_LOADER" approach let me know. > > The new loader schema split the jar in 3 categories : > > 1) container only (ie only used by tomcat) TOMCAT_HOME/lib/container > 2) application only (only needed by webapps) TOMCAT_HOME/lib/apps > 3) common (used by webapps and tomcat) TOMCAT_HOME/lib/common -- Jason Novotny [EMAIL PROTECTED] Home: (510) 704-9917Work: (510) 486-8662 NERSC Distributed Computing http://www-didc.lbl.gov
RE: NEW_LOADER in m1 tomcat.sh
>Can someone please tell me more about this change in the tomcat.sh >startup script? It looks like jars in TOMCAT_HOME/lib are no longer >geting added to the classpath- is this the new model? In my project >I like to deploy the jars directly to TOMCAT_HOME/lib where >they will be >found when Tomcat starts up. If someone knows what I should do >under the >"NEW_LOADER" approach let me know. The new loader schema split the jar in 3 categories : 1) container only (ie only used by tomcat) TOMCAT_HOME/lib/container 2) application only (only needed by webapps) TOMCAT_HOME/lib/apps 3) common (used by webapps and tomcat) TOMCAT_HOME/lib/common
