On 12/06/07, David Delbecq <[EMAIL PROTECTED]> wrote:
[..]
1) revise war build process to force inclusion of libs
2) have a server lifecyclelistener that, before loading of a webapp,
copy the concerned classes to the WEB-INF/lib ?
Copy seems easier than play with classloader...
Here is my so
On 12/06/07, David Delbecq <[EMAIL PROTECTED]> wrote:
[..]
Stupid suggestion:
Hehe, stupid approach requires stupid solutions ;]
What about one of those approach
1) revise war build process to force inclusion of libs
2) have a server lifecyclelistener that, before loading of a webapp,
copy
Hamster a écrit :
> On 12/06/07, David Delbecq <[EMAIL PROTECTED]> wrote:
>> 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?
>
> Don't ask me!
> It i
On 12/06/07, David Delbecq <[EMAIL PROTECTED]> wrote:
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?
Don't ask me!
It is their request, they said some
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:
>
>
>
On 12/06/07, Jon Wingfield <[EMAIL PROTECTED]> wrote:
You can supply a custom loader for a webapp to do this sort of thing:
http://tomcat.apache.org/tomcat-5.5-doc/config/loader.html
Each webapp would require a context.xml to enable the custom loader.
Thank you Jon for this tip, so according to
You can supply a custom loader for a webapp to do this sort of thing:
http://tomcat.apache.org/tomcat-5.5-doc/config/loader.html
Each webapp would require a context.xml to enable the custom loader.
Regards,
Jon
Hamster wrote:
Hi,
In resin, there is a possibility to configure it with following:
Hi,
In resin, there is a possibility to configure it with following:
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 custome
