tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 36231] - getCause() null for ServletException
Date Thu, 18 Aug 2005 17:29:19 GMT
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 junk@bbs.darktech.org  2005-08-18 19:29 -------
Guys, you don't need initCause() to fix this problem, nor do you need to change
the interface or specification. All you need to do is implement a method

public Throwable getCause()
{
  return getRootCause();
}

there you go. This code will run on J2EE 1.3 just fine and this is something
that the Tomcat team can do independantly of the specification. I also don't
understand what "portability" has anything to do with this (maybe you meant
backwards compatibility?). The way I see it, if someone is coding a webapp on
pre-1.3, he can't possibly invoke getCause() because it does not exist. If he
codes his webapp post-1.3, he expects getCause()'s contract to be met and we are
in fact trying to fix ServletException so it meets its contract. There is no
loss of "portability" or backwards compatibility here. Can I reopen this issue?

-- 
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: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message