On Tue, 25 Dec 2001, marc fleury wrote:
> Its' 7 lines of code (really) so unless someone has a fundamental
> religious problem with typed lookups I will add this in.
Well, if the object being returned by the lookup is supposed to be the
MBean then 'typed' anything assumes a bit much (which is w
implemented a given
interface (aka JINI) but still live in a detached world to allow for
infinite plugability (aka JMX).
--jason
- Original Message -
From: "marc fleury" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 25, 2001 10:13 PM
Subject
> This makes alot of sence... almost so that I wonder
> why the JMX folks did
> not make it this way from the start... perhaps the
> JINI guys wanted all the
> glory.
Jason, I really like the "ra-ra-ra-ism" of your attitude, that being said, the JMX
folks didn't do it this way for a good reason
MBeanServer.invoke() calls can be done away with too?
--jason
- Original Message -
From: "marc fleury" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 25, 2001 9:05 PM
Subject: [JBoss-dev] Lookup Registry by Class
> from the depth of the dep
from the depth of the deployers,
I am actually thinking of something slightly different that might help you guys. I
use the new org.jboss.system.Registry to lookup native MBean interfaces in the server,
it an intuitive way to hook up components in the run-time. Right now I lookup by
ObjectNa
