DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=38374>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38374 ------- Additional Comments From [EMAIL PROTECTED] 2006-02-16 12:23 ------- > The original RequestProcessor is just as constrained in 1.3 > by the fact that the process() method only throws IOException > and ServletException (unless we wanted to wrap the whole contents > of process() in a try catch). Yes, you're right. I tested everything with the new ComposableRequestProcessor, but not with the legacy RequestProcessor. So the legacy RP has not been tested against the applications at all. I'll update the legacy RP, reconfigure the applications locally, and run through all the tests again. The RP is the very core of the framework, and we should not just assume that it still works. I'm beginning to see supporting the original RP as a problem, since a lot of the testing is still manual, and now we have to do it all twice -- everytime we release any of the subprojects! If the new CRP seems to work well in 1.3.0, we should probably deprecate the legacy RP in 1.3.1, so that it could be removed in a 1.4 release. I'll also update the checklist to include testing applications using both versions. -Ted. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
