[
https://issues.apache.org/jira/browse/EXTCDI-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved EXTCDI-232.
----------------------------------
Resolution: Fixed
> introduce a new RestScope for better GET support
> ------------------------------------------------
>
> Key: EXTCDI-232
> URL: https://issues.apache.org/jira/browse/EXTCDI-232
> Project: MyFaces CODI
> Issue Type: New Feature
> Components: Core, JEE-JSF20-Module
> Affects Versions: 1.0.1
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.0.2
>
>
> For pages which are available per GET which uses <f:viewParam /> we often
> have the problem that @ViewAccessScoped is too aggressive in destroying beans
> if the >user opens the link in a new tab< (because the first request is done
> with the window-id of the first tab which causes the destroy of such beans
> >if< the navigation target is a different page. a custom js triggers a 2nd
> request with a new window-id to avoid cloning the window, but the first
> request already triggered the cleanup), but we still need to get new
> contextual instances once the GET parameters got changed.
> By introducing a new @RestScoped and the respective Context implementation we
> can provide exactly that. A @RestScoped is a sub-context of @WindowScoped,
> thus every new browser tab will get a new contextual instance.
> The RestScope is basically a CODI Conversation (1 bean == 1 conversation)
> very similar to @ViewAccessScoped. The only difference is that those 2 have
> different expiry calculation mechanism.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
