[
https://issues.apache.org/jira/browse/MYFACES-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated MYFACES-3214:
------------------------------------
Resolution: Fixed
Fix Version/s: 2.1.2
2.0.8
Assignee: Leonardo Uribe
Status: Resolved (was: Patch Available)
Yes, it sounds like some leftover from JSF 1.2
> Remove exception wrapping with FacesException and with getPathToComponent
> -------------------------------------------------------------------------
>
> Key: MYFACES-3214
> URL: https://issues.apache.org/jira/browse/MYFACES-3214
> Project: MyFaces Core
> Issue Type: Sub-task
> Components: General
> Reporter: Martin Kočí
> Assignee: Leonardo Uribe
> Priority: Minor
> Fix For: 2.0.8, 2.1.2
>
> Attachments: MYFACES-3214.patch
>
>
> some old code uses:
> catch(Exception ex)
> {
> throw new FacesException("Could not retrieve value of component
> with path : "+
> getPathToComponent(component),ex);
> }
> to provide path to problematic component. With JSF 2.0 and exception handler
> is is not necessary (and only makes stacktrace harder to read), because:
> 1) exception is always queued with component instance (see MYFACES-3201)
> 2) every EL expression knows about it's location (MYFACES-3202)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
