[
https://issues.apache.org/jira/browse/MYFACES-3202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe reopened MYFACES-3202:
-------------------------------------
It seems the patch v2 does not have the part that goes on ErrorPageWriter, so
it was not committed.
Additionally, I think this feature should have some config param to
enable/disable (enabled by default).
> Improve EL Exceptions wrapping
> ------------------------------
>
> Key: MYFACES-3202
> URL: https://issues.apache.org/jira/browse/MYFACES-3202
> Project: MyFaces Core
> Issue Type: Sub-task
> Components: General
> Reporter: Martin Kočí
> Assignee: Martin Kočí
> Priority: Minor
> Fix For: 2.0.8, 2.1.2
>
> Attachments: MYFACES-3202-ErrorPageWriter.patch,
> MYFACES-3202-screenshot.png, MYFACES-3202-v2.patch, 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: http://www.atlassian.com/software/jira
