myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo Uribe (JIRA)" <>
Subject [jira] [Commented] (MYFACES-3202) Improve EL Exceptions wrapping
Date Tue, 12 Jul 2011 01:20:59 GMT


Leonardo Uribe commented on MYFACES-3202:

I think in this case it could be better to extend the original exceptions with alternate ones
that provide the additional info. In that way, the previous behavior will be preserved. I
don't have clear if it is necessary to preserve it, but my first intuition makes me believe

> Improve EL Exceptions wrapping
> ------------------------------
>                 Key: MYFACES-3202
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Sub-task
>          Components: General
>            Reporter: Martin Kočí
>            Priority: Minor
>         Attachments: MYFACES-3202.patch
> From MYFACES-3053 "user should see not just a cryptic stack trace, but the EL expression
that was being evaluated  including the part of the EL expression that triggered the problem"
> Myfaces utilize TagValueExpression and TagValueExpressionUEL as TagAtrribute-aware wrappers
around EL ValueExpression. But this "context" is  only .toString()  of TagAttribute and that
prohibits user-frendly formatting of messages.
> Provide TagAttribute instance, create TagAttributeAwareExceptionWrapper that will hold
this instance. Clients (mainly ErrorPage) can read attributes of TagAttribute and format it
as necessary, for example "EL expression that triggered the problem: " + wrapper.getTagAttribute().getValue()

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message