This content has been marked as final.
Show 4 replies
-
1. Re: Mbean dependency resolution
raja05 May 7, 2004 2:24 AM (in response to aseembansal)Have a optional-attribute-name attribute for ur depends clause, something like
<depends optional-attribute-name="dependBean">objectname</depends>
And create a setter and getter for dependBeanprivate ObjectName dependObjName; public ObjectName getDependBean() { return this.dependBean; } and then use it as <Depend>MBean obj = (<depend>MBean) getServer().getAttribute(this.dependBean);
Check out jboss-service.xml for similar examples -
2. Re: Mbean dependency resolution
aseembansal May 7, 2004 2:33 AM (in response to aseembansal)Thanks for the reply.
Is this the only way to resolve the dependencies? In this case, a service has to expose getter/setter methods just to resolve the dependencies of dependents.
Is not there any componentRegistry in JBoss which maintains a mapping of objectName Vs objects.
-Aseem -
3. Re: Mbean dependency resolution
raja05 May 7, 2004 4:20 AM (in response to aseembansal)Ofcourse there is, the MBeanRegistry implementation in jboss does have this. getServer().getAttribute(this.dependBean); is going to take this value from the Registry and return the MBean associated with the object name,
-
4. Re: Mbean dependency resolution
aseembansal May 7, 2004 5:17 AM (in response to aseembansal)Thanks. That was what I was looking for.
-Aseem