You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org> on 2013/10/07 10:56:42 UTC

[jira] [Resolved] (MYFACES-3798) protected-view handling is broken

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

Gerhard Petracek resolved MYFACES-3798.
---------------------------------------

    Resolution: Not A Problem

agreed. i had to check a 3rd party code + a test which showed the issue. however, the real issue is in the 3rd party code (a quite hidden and dirty reassignment of _protectedViewsSet via reflection).

> protected-view handling is broken
> ---------------------------------
>
>                 Key: MYFACES-3798
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3798
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-344
>    Affects Versions: 2.2.0
>            Reporter: Gerhard Petracek
>            Assignee: Leonardo Uribe
>
> the result of ViewHandlerImpl#getProtectedViewsUnmodifiable isn't spec. compliant.
> addProtectedView and removeProtectedView don't recreate _unmodifiableProtectedViewsSet. at the end of both we need:
> _unmodifiableProtectedViewsSet = Collections.unmodifiableSet(_protectedViewsSet);
> or we always return Collections.unmodifiableSet(_protectedViewsSet); in ViewHandlerImpl#getProtectedViewsUnmodifiable



--
This message was sent by Atlassian JIRA
(v6.1#6144)