> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 02, 2003 10:50 AM > To: Tomcat Developers List > Subject: RE: [next] What's next ? > > > 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. >
-1 where would we put native libraries? I can't put them in /WEB-INF/lib without giving up reloading. I don't think we want to encourage people to put anything in the jvm's lib directory now that we got rid of classpath hell. I could see combining 'shared' and 'common' since they are essentially the same. Charlie --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
