[seam-issues] [JBoss JIRA] Commented: (SEAMFACES-44) View scope problems

Dan Allen (JIRA) jira-events at lists.jboss.org
Wed Jan 5 04:16:01 EST 2011


    [ https://issues.jboss.org/browse/SEAMFACES-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573390#comment-12573390 ] 

Dan Allen commented on SEAMFACES-44:
------------------------------------

See also: http://seamframework.org/Community/CannotSerializeSessionAttributeOrgapachemyfacesviewfaceletsDefaultFaceletsStateManagementHelperSERIALIZEDVIEWForSession4F66763ACB1F009D75674C8225413B30JavaioNotSerializableExceptionOrgjbossweldbeanManagedBean#comment144769

Partial quote:

"ViewScope is just not ready, cause its damn buggy. First of all there is the chicken egg problem when using partial state saving AND viewscope AND forEach. Second there is the bug with NotSerializableException. The root of the problem is that the ViewScope implementation is doing this:

Map<String, Object> viewMap = getViewMap();
Map<Contextual<?>, Object> map = (ConcurrentHashMap<Contextual<?>, Object>) viewMap.get(COMPONENT_MAP_NAME);

Contextual<?> is implemented by org.jboss.weld.bean.ManagedBean. So the an instance of org.jboss.weld.bean.ManagedBean is used in the map named "map" as key. The map is stored in the viewMap which is the default view map of jsf obtained in this way: viewRoot.getViewMap() . This viewMap is stored in the session.

So what ever is doing serialization of the session WILL NOT BE ABLE TO DO SO. Using this ViewScope breaks the ability of storing the viewScope on client side, sharing sessions between cluster nodes, recovering sessions after reload of a webapp/context and many more."

> View scope problems
> -------------------
>
>                 Key: SEAMFACES-44
>                 URL: https://issues.jboss.org/browse/SEAMFACES-44
>             Project: Seam Faces
>          Issue Type: Bug
>    Affects Versions: 3.0.0.Alpha3
>         Environment: glassfish v3.0.1
>            Reporter: Aleksandar Pejovic
>             Fix For: 3.0.0.Beta3
>
>         Attachments: viewscoped-problem.zip
>
>
> 1.View scope should behave like normal scope, but client proxies aren't being used.
> 2.View scoped beans should be passivation capable, but the container isn't enforcing that.
> 3. at ViewScoped annotation cannot be used on producer methods/fields.
> More detailed description is available on a forum:
> http://seamframework.org/Community/SeamfacesViewScopeProblems

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the seam-issues mailing list