[jboss-jira] [JBoss JIRA] Resolved: (JBAS-5155) DistributedReplicantManager - Add lookup method to that given a replicant name, returns a List of ClusterNode

[Galder Zamarreno (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-5155?page=all ]

Galder Zamarreno resolved JBAS-5155.
------------------------------------

    Resolution: Done

Interface changed in standalone cluster/ha-server-api project 
and implementation provided in AS cluster project.

> DistributedReplicantManager - Add lookup method to that given a replicant name, returns a List of ClusterNode
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-5155
>                 URL: http://jira.jboss.com/jira/browse/JBAS-5155
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions:  JBossAS-5.0.0.Beta3
>            Reporter: Galder Zamarreno
>         Assigned To: Galder Zamarreno
>             Fix For: JBossAS-5.0.0.Beta4
>
>
> I could do with having a method in DRM like this:
> public List<ClusterNode> lookupReplicantsNodes(String key);	
> and deprecate lookupReplicantsNodeNames() as it returns a List of String names, which could 
> still be accessible via ClusterNode.getName(). Otherwise, building a List of ClusterNode from, 
> for example. the singleton service name is inefficient. I have to take the singleton name, look 
> up the List of Cluster Node names, and with that list, take ClusterNode list from the partition and 
> match them to create a brand new ClusterNode list with the nodes where the singleton are 
> running. ugh

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira