You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2012/05/22 17:52:40 UTC

[jira] [Updated] (MYFACES-3501) Remove unncecessary exception wrapping

     [ https://issues.apache.org/jira/browse/MYFACES-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leonardo Uribe updated MYFACES-3501:
------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.8
                   2.0.14
           Status: Resolved  (was: Patch Available)
    
> 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
>             Fix For: 2.0.14, 2.1.8
>
>         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