Re: cvs commit: jakarta-tomcat-4.0/catalina/src/bin catalina.bat catalina.sh

["Craig R. McClanahan" <Cr...@eng.sun.com>]

Scott Sanders wrote:

> Craig, is there a reason you took this loop out.  Are we to just pass in a
> full classpath.  I am wondering as I am using the JDBC Realm with MySQL and
> it cannot find the driver since I updated tonight from M1.  Just wondering
> ;-)
>

Yes, there is a reason.  The "shared extensions" class path is now built (from
the contents of the "$CATALINA_HOME/lib" directory) internal to Catalina.  That
way, there are no problems with classpath lengths or syntax that were causing
us so much grief with Tomcat 3.x.  These classes are all visible to
applications, but not to Catalina itself.

If you want Catalina itself to see the classes (as you would for a JDBC driver
for the JDBCRealm), you need to put a copy of that driver into
"$CATALINA_HOME/server" instead.  That's where the files for the container
itself get assembled into a separate classloader that is not visible to
applications.

There is a document in the source tree (catalina/docs/dev/classloaders.html)
that describes the class loading environment in more detail.

>
> Scott
>

Craig


>
> >   1.6       +1 -5      jakarta-tomcat-4.0/catalina/src/bin/catalina.sh
> >
> >   Index: catalina.sh
> >   ===================================================================
> >   -
> >   -#for i in $CATALINA_HOME/lib/*.jar ; do
> >   -#  CP=$CP:$i
> >   -#done
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org

--
====================
See you at ApacheCon Europe <http://www.apachecon.com>!
Session VS01 (23-Oct 13h00-17h00):  Sun Technical Briefing
Session T06  (24-Oct 14h00-15h00):  Migrating Apache JServ
                                    Applications to Tomcat