Details
Bug
Major
Description
The window ID is generated on the server but the active portlets in the window do not share the same window ID. This causes unnecessary DOM diffs and possibly the malfunction of the window scope. In the past we discussed about this issue, one possible solution would be to let each portlet assign its own window ID and then send a list of window IDs during dispose-window request. Each portlet will then match only the window ID it knows about and dispose the corresponding scope.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Change dispose window code to use URL found in javax.faces.ecodedURL hidden input element. This way the request is properly invoking WindowScopeManager resource handler.
Show
Mircea Toma
added a comment - Change dispose window code to use URL found in javax.faces.ecodedURL hidden input element. This way the request is properly invoking WindowScopeManager resource handler.
Introduced Liferay specific strategy for sharing windowIDs between portlet instances belonging to same WAR. Refactored code to use Liferay specific strategy automatically or fallback to default timed heuristic strategy.
Show
Mircea Toma
added a comment - Introduced Liferay specific strategy for sharing windowIDs between portlet instances belonging to same WAR. Refactored code to use Liferay specific strategy automatically or fallback to default timed heuristic strategy.
Use of a ThreadLocal may provide isolation between simultaneous requests. The ThreadLocal should contain the Session ID to prevent collisions when a thread is later used to handle a request for a different session.
Show
Ted Goddard
added a comment - Use of a ThreadLocal may provide isolation between simultaneous requests. The ThreadLocal should contain the Session ID to prevent collisions when a thread is later used to handle a request for a different session.
Introduced time-based heuristic to assign same windowID and window scope to all portlets within the same WAR.