Remy Maucherat wrote: > > Adding another CL layer is dangerous and makes CL slower; > unless other people think this is useful I don't think we > should add the feature) >
Another option is to use the manifest version tags to identify which versions of the servletapi (and other sensitive classes) are being used, and print out an error message if they don't match what Tomcat requires. Patrick Luby wrote: > > My first concern is that Tomcat always can at least run no matter what > extensions that user has installed. Whether or not those extensions are > accessible to Tomcat is, IMHO, a feature that we may or may not want to > include. Quitely dropping extensions that the user has installed is unintuitve, and in some ways worse than the current situation. Perhaps a combination? Normal behavior is to check api versions, exit if they don't match. Fallback if it's impossible to remove the extensions is to use the "java.ext.dirs=" hack? That lets a user get Tomcat running no matter what, but with full awareness of the tradeoff. Either way, the current situation is a problem for many people, as can be seen by a quick scan of the tomcat-users list. -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
