myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerhard Petracek (JIRA)" <>
Subject [jira] [Commented] (EXTCDI-218) defer final deletion of @ViewAccessScoped beans
Date Tue, 30 Aug 2011 10:21:37 GMT


Gerhard Petracek commented on EXTCDI-218:

1) is already there
2) not needed (will be solved by 3) ) and adds additional complexity esp. for the manual usage
of the WindowContext api - maybe as optional feature if there is a problem with 3)
3) planned since a long time for all codi scopes - esp. for a better back-button support like
the swf repos but it requires a requst-id which might be part of the upcoming window-id prototype
for jsf 2.2 (a backport to jsf 2.0 and 2.1 is planned)

-> +1 for 3) -- we shouldn't do 2) for now because it creates new issues and is more like
a workaround. if someone needs it, it's possible to impl. it as codi-addon

> defer final deletion of @ViewAccessScoped beans
> -----------------------------------------------
>                 Key: EXTCDI-218
>                 URL:
>             Project: MyFaces CODI
>          Issue Type: New Feature
>          Components: JEE-JSF12-Module, JEE-JSF20-Module
>    Affects Versions: 1.0.1
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
> I have a tricky problem in production with @ViewAccessScoped beans in conjunction with
the lazy windowId dropping script
> The problem arises if the user is on the browsers tabA (windowId=123) which has a @ViewAccessScoped
bean and opens a link from this window in a new tabB.
> In this case a request with the old windowId=123 (*) will be sent to the server and the
response will be rendered to tabB. When the dropWindowId script detects that tabB is a fresh
browser tab, it will issue a new request and drops the windowId to get a new one (windowId=124
now for tabB)
> The problem is that in step (*) we get a request with the _old_ windowId onto a new view,
thus we drop the @ViewAccessScoped bean used in tabA.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message