[
https://issues.apache.org/jira/browse/MYFACES-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281031#comment-13281031
]
Leonardo Uribe commented on MYFACES-3501:
-----------------------------------------
Just for the record, checking the code I notice these patches relies on the
commit done in rev:
#1300273
#1300275
#1305497
#1305498
Related to MYFACES-3199 Handling AbortProcessingException is unconsistent,
which added the unwrapping code for AbortProcessingException inside
UIViewRoot._broadcastAll().
> Remove unncecessary exception wrapping
> --------------------------------------
>
> Key: MYFACES-3501
> URL: https://issues.apache.org/jira/browse/MYFACES-3501
> Project: MyFaces Core
> Issue Type: Sub-task
> Components: General
> Reporter: Martin Kočí
> Assignee: Martin Kočí
> Priority: Trivial
> Attachments: ActionListenerImpl.patch, RendererUtils.patch,
> TextInstruction.patch, UIComponentBase.patch
>
>
> Similar to MYFACES-3214:
> ld 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 and
> MYFACES-3199)
> 2) every EL expression knows about it's location (MYFACES-3202)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
