You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Michael Freedman (JIRA)" <de...@myfaces.apache.org> on 2009/08/12 20:19:14 UTC

[jira] Resolved: (PORTLETBRIDGE-92) Refresh of faces view using client-side state saving fails (in Mojarra) with class cast expection of PortletUIViewRootNamingContainer

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

Michael Freedman resolved PORTLETBRIDGE-92.
-------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
                   1.0.0

As indicated -- the bridge impls faces-config.xml now excludes this attribute.

> Refresh of faces view using client-side state saving fails (in Mojarra) with class cast expection of PortletUIViewRootNamingContainer
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: PORTLETBRIDGE-92
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-92
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>          Components: Impl
>    Affects Versions: 1.0.0-beta, 2.0.0-alpha
>            Reporter: Michael Freedman
>            Assignee: Michael Freedman
>             Fix For: 1.0.0, 2.0.0
>
>
> When client side state saving is used, the Mojarra impl depends on a com.sun.faces.util attribute -- this attribute at first holds the tree structure -- but as its activated the tree structure is changed from holding tree nodes to the actual faces components (restored).  If this attribute is retained across requests (i.e. in the bridge's scope) you get a classCastException if the page the portlet is on is refreshed.  This is because it stays around and hence holds the restored components rather than the nodes.
> Anyway, simple fix is to add com.sun.faces.util.* to the bridge's excluded attributes list maintained in its faces-config.xml.

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