[jira] Resolved: (MYFACES-2787) Application objects which can be wrapped must not access public methods internally

["Jakob Korherr (JIRA)" <de...@myfaces.apache.org>]

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

Jakob Korherr resolved MYFACES-2787.
------------------------------------

    Fix Version/s: 2.0.1-SNAPSHOT
       Resolution: Fixed

> Application objects which can be wrapped must not access public methods internally
> ----------------------------------------------------------------------------------
>
>                 Key: MYFACES-2787
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2787
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-314
>    Affects Versions: 2.0.1-SNAPSHOT
>            Reporter: Jakob Korherr
>            Assignee: Jakob Korherr
>             Fix For: 2.0.1-SNAPSHOT
>
>
> Some time ago there was an issue with Trinidad that was caused by a wrapper which added some functionality to the standard implementation (MYFACES-2641). The problem was that the standard implementation (of ViewHandler in this case) used other public methods internally via this.method() instead of invoking them on the wrapper. Thus the wrapper was circumvented which led to loss of the additionaly functionality.
> I now finally took a look at all those affected classes and found some similar issues, which could cause problems in wrapped environments. One of them is in ViewHandlerImpl when getting the ViewDeclarationLanguage via this.getViewDeclarationLanguage(). This should be done by facesContext.getApplication().getViewHandler().getViewDeclarationLanguage().

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.