Remy Maucherat wrote:
>
> > The above changes remove one class loading layer from a web app,
> > allows Common classes to use property files and resources, and cleans
> > up the directories where jar files and classes are located.
>
> The Catalina core would see the shared libraires, which is a very bad idea
> IMO. We'll get into the same kind of class conflicts and sealing violations
> we now face because Jasper uses JAXP 1.1.
> I really can't see any real benefits (but I can see a lot of problems) in
> removing the shared class loader.
>
Thats right! Ok, I retract my proposal for changing the class loaders.
> What we can do is add a lib/classes/ repository to the shared classloader.
>
I still think it would be a good idea to change the directory structure of
where the lib/classes are located to make it clearer where to install
libraries/resources.
System class loader uses jars located in
$CATALINA_HOME/system/lib
$CATALINA_HOME/system/classes
Common class loader uses jars/classes/resources located in
$CATALINA_HOME/common/lib
$CATALINA_HOME/common/classes
Shared class loader for web applications uses jars/classes/resources located in
$CATALINA_HOME/lib
$CATALINA_HOME/classes
Catalina private jars/classes/resources located in
$CATALINA_HOME/server/lib
$CATALINA_HOME/server/classes
The classes directories would only be added to the list of URL's for
a class loader if it exists
And remove servlet.jar and naming.jar from the catalina.sh start script.
Regards,
Glenn
----------------------------------------------------------------------
Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder |
MOREnet System Programming | * if iz ina coment. |
Missouri Research and Education Network | */ |
----------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
