[
https://issues.jboss.org/browse/SEAMFACES-44?page=com.atlassian.jira.plug...
]
Mark Struberg commented on SEAMFACES-44:
----------------------------------------
Allow me to disagree. It would not make things easier but would break the EE spec. The
@ViewScoped is per the JSF spec backed by the JSF ViewMap. The JSF ViewMap gets serialized
into the View with every request. And THAT is what people expect!
If there is a problem with Serializing Contexts then please fix it! I know there are
currently not much tests for serialization in the TCK, but the behaviour of passivating
scopes is clearly well defined!
Please go on and fix all this nasty serialisation problems in the core. You will see that
50++ bugs will silently go away after that...
View scope problems, feature needs review
-----------------------------------------
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.1.0.Final
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.@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