Based on all the recent traffic from people tying themselves into pretzels with global resources, I have two concrete ideas. I would try to concoct patches (at least for the first) if there was tentative acceptance for either. 1) Configure the 'common' classpath in an editable location. By default, this path would be the current set of common directories. However, an admin could add additional directories shaped like common. This would be an improvement in administration. As things are, if I want to distribute/deploy common resources, I have to mix my stuff in with the standard stuff. A new release of Tomcat requires me sort it all out over and over. It would cleaner if I could keep 'my' stuff off in separate directories, and just configure it into Tomcat. If I had multiple packages from multiple sources that needed to go into common, I could keep them separate. 2) Some sort of optional classpath conflict checker. Many people seem to get into deep trouble by ending up with copies of 'the same thing' in both a webapp class path and the common class path. I'm thinking of an off-to-one-side tool that would inventory the contents of a webapp, and check for conflicts with common, and report them. Perhaps this would be a candidate for merely 'contrib' status if someone coded it.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
