You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Simon Kitching (JIRA)" <de...@myfaces.apache.org> on 2008/01/13 00:22:34 UTC

[jira] Commented: (MYFACES-1802) FacesException and nested exceptions

    [ https://issues.apache.org/jira/browse/MYFACES-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558311#action_12558311 ] 

Simon Kitching commented on MYFACES-1802:
-----------------------------------------

This looks good to me. And yes I think serialVersionUID does need to be updated.

However I see a dozen places elsewhere in the api module code where Throwable.getCause() is being called, so they would also need to be somehow fixed. It's clear that no-one has tried to run this on java 1.3 for a very long time..

> FacesException and nested exceptions
> ------------------------------------
>
>                 Key: MYFACES-1802
>                 URL: https://issues.apache.org/jira/browse/MYFACES-1802
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-127
>    Affects Versions: 1.1.5
>            Reporter: Bernhard Huemer
>         Attachments: MyFaces-1802.patch
>
>
> The JSF 1.1 specification requires any implementation to support Java 1.3 and that's why the FacesException isn't allowed to utilize builtin exception chaining mechanisms (i.e. initCause(), etc..) as they have been introduced in Java 1.4. However, the FacesException retains it's cause by delegating to the parent's constructor (for example, "super(cause);" or "super(message, cause);"). 
> Although this bug is rather easy to fix, I've assigned the priority level 'Major' as it breaks the specification.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.