I wasn't trying to be rude. I was just summing up a fairly large
discussion that touched on everything from classloader sharing to
security to where any changes would reside.
You want several web apps to have access to the same jar file as
if each had their own private version, ie: no sharing of static data
or security permissions or any of that.
-Paul Speed
Rick Mann wrote:
>
> on 8/30/01 11:36 PM, Paul Speed at [EMAIL PROTECTED] wrote:
>
> > Just clarifying, you basically want the exact same functionality
> > you'd get by copying the jars into the individual webapp lib
> > directories, but you just don't want to have to copy them. Right?
>
> Look, if it were the exact same functionality as copying the classes/jars
> into the individual webapp's folders, then that's what I'd do.
>
> However, it's not the same thing. It makes deployment and development more
> difficult, despite the possibility of creating scripts or ant files to
> automate this process, it's still not as easy as being able to put the
> classes in one place once.
>
> If it makes you happy, yes. I want the exact same functionality as copying a
> set of class files/jar files into a subset of installed webapp's directories
> without copying them or making links from one dir to another.
>
> ------------------------------------------------------------
> Roderick Mann rmann @ latencyzero.com.sansspam
