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
: 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
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
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 ::
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
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
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
