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

[ https://issues.jboss.org/browse/SEAMFACES-44?page=com.atlassian.jira.plug... ] Dan Allen commented on SEAMFACES-44: ------------------------------------ See also: http://seamframework.org/Community/CannotSerializeSessionAttributeOrgapac... 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." -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira