[jboss-jira] [JBoss JIRA] Updated: (JBCLUSTER-78) Handling of merge
Brian Stansberry (JIRA)
jira-events at lists.jboss.org
Tue May 18 17:18:06 EDT 2010
[ https://jira.jboss.org/browse/JBCLUSTER-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry updated JBCLUSTER-78:
--------------------------------------
Fix Version/s: Legacy
(was: Q3Y8)
Moving issues not directly related to code developed in https://svn.jboss.org/repos/jbossas/projects/cluster to "Legacy" Fix Version.
> Handling of merge
> -----------------
>
> Key: JBCLUSTER-78
> URL: https://jira.jboss.org/browse/JBCLUSTER-78
> Project: JBoss Clustering
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Bela Ban
> Assignee: Brian Stansberry
> Fix For: Legacy
>
>
> All building blocks which involve state do *not* implement handling of merging. E.g. DRM.mergeMembers() should invoke a callback so that each subscribed listener can handle the merge.
> This needs to be done for the existing building blocks for backward compatibility, the new mechanism used is JBossCache (see link) which will handle state merging
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list