[
https://jira.jboss.org/browse/JBCLUSTER-271?page=com.atlassian.jira.plugi...
]
Brian Stansberry moved JBAS-7850 to JBCLUSTER-271:
--------------------------------------------------
Project: JBoss Clustering (was: JBoss Application Server)
Key: JBCLUSTER-271 (was: JBAS-7850)
Component/s: HA-Server-API
(was: Clustering)
Fix Version/s: HA-Server-API 2.0.0.Beta1
(was: 6.0.0.M4)
Decouple distributed locking code from HAPartition
--------------------------------------------------
Key: JBCLUSTER-271
URL:
https://jira.jboss.org/browse/JBCLUSTER-271
Project: JBoss Clustering
Issue Type: Task
Security Level: Public(Everyone can see)
Components: HA-Server-API
Reporter: Brian Stansberry
Fix For: HA-Server-API 2.0.0.Beta1
org.jboss.ha.framework.server.lock.AbstractClusterLockSupport is too tied to HAPartition.
It needs access to:
1) A generic RPC invocation mechanism
2) Membership change notifications.
Those could be implemented via a full HAPartition impl, via hacks on top of Infinispan,
via direct use of RpcDispatcher, etc. So don't require the full HAPartition API.
Probably the thing to do is have HAPartition itself become a composition of other, more
focused interfaces. These would mean a change in ha-server-api project. Then
AbstractClusterLockSupport could consume the relevant sub-interfaces.
--
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