What's the point? Saving 2 Megs of hard disk space and, at the same
time, risk to break deployed apps that sudeently get additionnal libs
that can conflit in version with vendor supplied one?
Hamster a écrit :
> Hi,
> In resin, there is a possibility to configure it with following:
>
> <web-app-default>
> <!--
> - Extension library for common jar files. The ext is safe
> - even for non-classloader aware jars. The loaded classes
> - will be loaded separately for each web-app, i.e. the class
> - itself will be distinct.
> -->
> <class-loader>
> <tree-loader path="${server.rootDirectory}/ext-webapp"/>
> </class-loader>
>
> When above configuration is used then each jar placed in ext-webapp
> directory is loaded for each web-app X1, X2, ... just like it would be
> placed in X1/WEB-INF/lib, X2/WEB-INF/lib, ...
>
> Our customer asked us if it is possible in Tomcat.
>
> According to
> http://tomcat.apache.org/tomcat-5.5-doc/class-loader-howto.html
> it is not possible, could you please confirm or give me any tip or
> idea (I know that it is not correct approach - but it is customer
> request - cannot do much about it ;)).
>
> Maybe there is a way to extend Tomcat, maybe there is already a
> solution of this problem?
>
> Thanks,
> Hamster
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
