myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernhard Huemer (JIRA)" <>
Subject [jira] Commented: (MYFACES-1802) FacesException and nested exceptions
Date Sun, 13 Jan 2008 11:15:34 GMT


Bernhard Huemer commented on MYFACES-1802:

The problem is that it seems that noone is using MyFaces 1.1.x in a Java 1.3 environment,
but everyone "suffers" from the resulting performance impact. I wouldn't pay attention to
every single case where we can improve MyFaces 1.1.x for users still working in a Java 1.3
environment (at least not if there's an impact for our actual userbase and keep in mind that
obviously noone has been using MyFaces 1.1.x in a Java 1.3 environment!). Note that the Spring
2.5 developers have dropped Java 1.3 support  ..

Simon, I guess I have to admit that I can't find something regarding method linkage in the
JLS either, but then we can still introduce an additional indirection, for example by using
an interface "ExceptionCauseRetriever" with two implementations, one assuming that it is running
a Java >= 1.4 environment and the other one using reflection to support backward compatible
exceptions too (just as Mario suggested).

> FacesException and nested exceptions
> ------------------------------------
>                 Key: MYFACES-1802
>                 URL:
>             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.

View raw message