[
https://issues.apache.org/jira/browse/MYFACES-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558381#action_12558381
]
Bernhard Huemer commented on MYFACES-1802:
------------------------------------------
Introducing a new interface with two implementations ... it seems that I've
overengineered the problem a little bit. As we only use reflection in an error
case, I think it's fine if we keep status quo (i.e. the changes that Simon has
commited).
> 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
> Fix For: 1.1.6-SNAPSHOT
>
> 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.
