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=36231>. 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=36231 ------- Additional Comments From [EMAIL PROTECTED] 2006-04-27 22:26 ------- David, we've been waiting for a specification update for years now. Notice the BugParade issue was filed in 2000 (!!). I don't understand what you meant in your last post, about the latest patch breaking applications that invoke initCause(). Our constructor would invoke initCause(), then user code can do what it wants with the resulting exception. If they choose to invoke initCause() on it, it'll simply override the exception we set. I'm sorry but I don't understand what problems could occur...? Also, I wanted to say I totally agree with Jonathan. More often than not, the Tomcat developers I've dealt gave (totally invalid) excuses for why they cannot be bothered to fix bugs. Maybe that's why Glassfish came along. Anyway, I look forward to some point in the future when this situation changes for the better. -- 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]