Just a curious question to this, I know Dan has his setup already but is there any reason that this could not be set up the other way around? I mean that the classes/jars are in the normal spot in Tomcat and the outside app accesses them there. The outside app shouldn't care where the files reside as long as the path to them is known and this way Tomcat is a untouched normal install.


Or am I missing something here? I am just trying to learn.

Thanks

Doug


----- Original Message ----- From: "Tim Funk" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[email protected]>
Sent: Tuesday, March 01, 2005 10:37 AM
Subject: Re: Need access to classes outside Tomcat for JSPs



If you happen to change the bootstrap classpath - please do not email the list with ClassNotFound issues. ;)

If you really need to access jar's or classes outside of your webapp you can either:
1) Write your own WebAppClassloader - icky but doable
2) Change $CATALINA_HOME/conf/catalina.properties and change either the common or shared loader. This is more managable but all webapps will share these classes.


Adding your own classes to the system classpath will cause major headaches. Adding common libraries to the common or shared classloader typically is the least of all evils when you can't place classes inside WEB-INF.

-Tim

Dan wrote:

Just as soon as I hit send....

Registry entry.

HKLM | Software | Apache Software Foundation | Procrun 2.0 | Tomcat5 | Parameters | Java

Classpath = .;e:\java\library\basic;e:\java\library\custom;E:\java\Tomcat\bin\bootstrap.jar

--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]






--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to