[ mx4j-Bugs-859086 ] RelationService.getRelation not setting m_proxy

Bugs item #859086, was opened at 2003-12-12 10:38
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450647&aid=859086&group_id=47745

Category: JMX implementation
Group: Release 1.1.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: RelationService.getRelation not setting m_proxy

Initial Comment:
From: [email protected]

In RelationService.getRelation, under the condition 
where relationId corresponds to an ObjectName, the 
member m_proxy seems like it should be set to a proxy 
corresponding to the passed relationId, e.g. m_proxy = 
(RelationSupportMBean)StandardMBeanProxy.create
(RelationSupportMBean.class, m_server, (ObjectName) 
this.m_relationIdToRelationObject.get(relationId));

This means that getRelation will return a proxy for the 
last Relation to be passed to RelationService.addRelation.

The problem can be demonstrated by doing the following:

Call RelationService.addService passing an object name 
of a Relation with a set of roles.

Call RelationService.addService passing an object name 
of another relation with a different set of roles.

Call RelationService.getAllRoles passing the relation id of 
the second relation added.

You will see that the roles returned are actually those of 
the first relation added.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450647&aid=859086&group_id=47745


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click