> On 1/10/06, Oded Arbel <[EMAIL PROTECTED]> wrote: > >> >> An optimal setup for me, I think, is: >> - for each application to put the 3rd party dependencies in WEB-INF/lib >> (I'm using JPackage's build-jar-repository, which I auto invoke from >> the ant script, so its even automatic). > > I thought you said you were not able to the the classes into jar files > (as that was part of a separate build automation process) ?
No - I'm talking here about the 3rd party libraries, which I did not develop and are not part of tomcat - these come as jars. >> - for each application that users locally developed libraries to list >> their build directories in the web.xml so what the WebAppClassLoader >> can get at them without them being shared. >> > > There's no attribute in web.xml that let's you specify separate class > paths to load from. > > What you could do is to write your own WebAppClassLoader that'd add > these folders to its lookup list. Hmm. interesting. How can I let such a class loader implementation to be used instead of tomcat's WebAppClassLoader ? -- Oded --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
