tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject RE: [next] What's next ?
Date Thu, 02 Oct 2003 14:49:36 GMT
On Thu, 2 Oct 2003, Angus Mezick wrote:

> > 2. Eliminate the shared and common classloader repositories.  Unless
> > these are required by the spec?  Force webapps to be self-contained by
> > putting all their classes in WEB-INF/lib or WEB-INF/classes of their
> > webapp.  Have the WEB-INF/clases -> WEB-INF/lib -> endorsed -> system
> > classloader hierarchy, much simpler than current.
> -1 Ugh!  No.  I love the current format.  I have full control of what
> webapps are in use on my system and I don't wish to have to maintain the
> build config that has each of my 5 web apps copy from a central
> repository instead of just using commons.  I find the current solution
> rather elegant because I can use it but am not forced to.

Ack. In contrast, I've sometimes wished to have webapp (classloader)
hierarchies. A context nested in another context would see the outer
classes but would be independently restartable. However, if a parent
context is restarted, all children are restarted, too.

Matthias Ernst
Software Engineer

CoreMedia - Smart Content Technology

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message