[jira] [Updated] (LANG-767) Keep 'cause method names' in Lang 4.0 for ServletException

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (LANG-767) Keep 'cause method names' in Lang 4.0 for ServletException

AD_LB (Jira)

     [ https://issues.apache.org/jira/browse/LANG-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henri Yandell updated LANG-767:
-------------------------------

    Fix Version/s: 4.0
   

> Keep 'cause method names' in Lang 4.0 for ServletException
> ----------------------------------------------------------
>
>                 Key: LANG-767
>                 URL: https://issues.apache.org/jira/browse/LANG-767
>             Project: Commons Lang
>          Issue Type: Task
>          Components: lang.exception.*
>            Reporter: Jens Bannmann
>              Labels: deprecated
>             Fix For: 4.0
>
>
> http://commons.apache.org/lang/article3_0.html#Deprecations says:
> bq. The lone deprecation in 3.0 is that of the notion of 'cause method names' in ExceptionUtils. In Java 5.0 it is still just about needed to handle some JDK classes that have not been migrated to the getCause API. In Java 6.0 things appear to be resolved and we will remove the related methods in Lang 4.0.
> I see a problem with this plan: so far, javax.servlet.ServletException has not been retrofitted to make use of the getCause() API for chaining. In 2005, the Tomcat project rejected a [bug requesting this|https://issues.apache.org/bugzilla/show_bug.cgi?id=36231], stating that it had to be changed in the spec, and nothing seems to have happened since. [A bug at sun suggesting a spec change|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4395719] is still open as of today.
> Thus, if you remove all support for cause method names from ExceptionUtils in Lang 4.0, web application authors would be forced to either write support glue for ServletException themselves again, or keep a dependency for Lang 3.0 alongside. Both alternatives sound bad to me.
> How about removing most of the cause method names, but keeping those that are still required for dealing with widely used classes such as ServletException?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira