[jira] [Resolved] (SANTUARIO-297) Exceptions should use a JDK exception cause mechanism

["Colm O hEigeartaigh (Resolved) (JIRA)" <ji...@apache.org>]

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

Colm O hEigeartaigh resolved SANTUARIO-297.
-------------------------------------------

    Resolution: Fixed
    
> Exceptions should use a JDK exception cause mechanism
> -----------------------------------------------------
>
>                 Key: SANTUARIO-297
>                 URL: https://issues.apache.org/jira/browse/SANTUARIO-297
>             Project: Santuario
>          Issue Type: Improvement
>          Components: Java
>    Affects Versions: Java 1.5
>            Reporter: Giedrius Noreikis
>            Assignee: Colm O hEigeartaigh
>             Fix For: Java 1.5.1
>
>
> Is there any reason why all org.apache.xml.security.** exceptions still use own "originalException" field to indicate a cause instead of a standard JDK mechanism? Since Throwable.getCause() returns null in this case, this complicates exception handling when a root cause needs to be determined.
> Interestingly, this was fixed many years ago in r350797 and then rolled back (because a compatibility with JDK 1.3 was required, I guess). However, since the 1.5.0 release requires JDK 1.5, for me it seems logical to make some refactorings to get rid of this relic.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira