[EXTCDI-218] defer final deletion of @ViewAccessScoped beans

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.0.1
• Component/s: JEE-JSF12-Module, JEE-JSF20-Module
• Assignee: Mark Struberg
• Reporter: Mark Struberg
• Created: 30/Aug/11 07:02
• Updated: 06/Dec/11 07:08
• Resolved: 17/Oct/11 08:47

Description

I have a tricky problem in production with @ViewAccessScoped beans in conjunction with the lazy windowId dropping script
http://wiki.apache.org/myfaces/Drafts/WindowId

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.