Glenn Nielsen wrote: >> Personally, I'm willing to ignore the issue. >>
Then I'll ignore the issue as well. > If the decision is made that we can not do a Tomcat release without > all dependent jar files being at a final stable release then I would > rather push to get commons to do a final stable release of fileupload > than remove those features from the HTMLManager. No, the problem is that fileupload shouldn't be in server/lib regardless of version and release state, and HTMLManager shouldn't be bloated. > Regarding Cositn's issue with having fileupload.jar and > servlets-manager.jar > in /server/lib. I agree with him. Both the web application manager and > the webdav web application should be moved from the core of catalina to > packages org.apache.webapp.manager and org.apache.webapp.webdav > respectively. > > I am working on moving the Manager/HTMLManager from the catalina core > to the webapp itself. This is not as simple as just moving the jars > due to class loading issues and Resource Bundles. But it shouldn't > take too long. Sounds good. You should do this refactoring in tomcat5 first - I'm not sure it's even worth backporting. Regarding class loading - at least for tomcat5 we agreed that JMX will be required, and it can be used to implement all features of the manager without having to worry about class loaders. In addition, if JMX1.2 is used you can control access to individual operations - which is far more granular and powerfull than "all or nothing" approach with priviledged apps. ( it would be cool if the authenticated user could be used as Subject in the policy file :-) Costin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
