[
https://issues.apache.org/jira/browse/MYFACES-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070013#comment-13070013
]
Leonardo Uribe commented on MYFACES-3221:
-----------------------------------------
Looks good. Maybe the additional object creation cause a performance hit, but
is justified, so we can ignore it.
> Create and use structure for facelets Location and TagAttribute-aware
> exceptions
> --------------------------------------------------------------------------------
>
> Key: MYFACES-3221
> URL: https://issues.apache.org/jira/browse/MYFACES-3221
> Project: MyFaces Core
> Issue Type: Sub-task
> Components: General
> Reporter: Martin Kočí
> Assignee: Martin Kočí
> Priority: Minor
> Attachments: MYFACES-3221-draft.patch, MYFACES-3221.patch
>
>
> This can be considered as continuation of MYFACES-3202. Implements
> requirement "any time there is an error the 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"
> Example:
> <f:actionListener type="com.foo.Bazz" /> is represented as
> org.apache.myfaces.view.facelets.tag.jsf.core.ValueChangeListenerHandler.LazyValueChangeListener
> instance. But if look in code, you see simple
> valueChangeListener.processValueChange(event); without try catch. If
> exception occurs, no facelets Location or TagAttribute context is available
> and therefore exception handling mechanism is not able to output info about
> problematic XML tag.
> Use types created as part of MYFACES-3202 (ContextAware, LocationAware .. );
> create something like ExecuteTemplate and ExecuteCallback and perform all
> operation with proper context.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
