Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Invalid
-
Affects Version/s: 1.7.2 SP1, 1.8DR#2
-
Fix Version/s: None
-
Component/s: Framework
-
Labels:None
-
Environment:Any
Description
The current implementation of server-side (Ajax Push) render groups does not allow for easily failing over in a cluster. There needs to be support for checking for existing groups, adding to groups on the target node, creating groups that don't exist, etc. We should also have a sample application that shows how it might be possible to support this now and going forward.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Marking as Closed / Invalid as part of legacy ICEfaces 1.x, 2.x JIRA cleanup.
Note: This issue may be resolved in a newer ICEfaces release, available here: http://www.icesoft.org/java/downloads/icefaces-downloads.jsf
If the issue persists with the current ICEfaces release, please create a new JIRA for it.
Show
Ken Fyten
added a comment - Marking as Closed / Invalid as part of legacy ICEfaces 1.x, 2.x JIRA cleanup.
Note: This issue may be resolved in a newer ICEfaces release, available here: http://www.icesoft.org/java/downloads/icefaces-downloads.jsf
If the issue persists with the current ICEfaces release, please create a new JIRA for it.
Failover with Ajax Push does work in a constrained set of circumstances. The Renderable interfaces can be implemented on a request-scoped bean which handles all of the group membership logic on creation and destruction. When a page is reloaded on failover, the render groups are properly set up on the new node.
I'm re-targetting this case for 1.8DR#3 where we'll add support for session-scoped beans and the SessionRenderer API.