Perhaps once Marc's changes are commited we can look into make this a reality.
--jason On Wed, 12 Dec 2001, Bill Burke wrote: > Excellent idea. > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Jason > > Dillon > > Sent: Wednesday, December 12, 2001 5:08 PM > > To: [EMAIL PROTECTED] > > Subject: [JBoss-dev] more jmx domain structure > > > > > > Again, quick thought... > > > > Was thinking that we might want to change the way we use JMX > > domain names. > > Right now we have something like this: > > > > Adaptor > > J2EE > > JBOSS-SYSTEM > > JBossMQ > > JCA > > JMImplementation > > JMX > > Jetty > > Security > > SingleJBoss > > ZClassLoaders > > > > This does not really show which bits are specific to JBoss, which > > are part > > of the JMX reference impl and which bits might be user components. So, I > > was thinking something more DNS like: > > > > jboss.system > > jboss.system.classloaders > > jboss.mq > > jboss.jmx > > jboss.jmx.adaptor > > jboss.jca > > jboss.j2ee > > jboss.security > > jboss.management > > jboss.web > > > > Then users might specify components like: > > > > user.mydomain > > user.mydomain.subdomain > > > > I think that this would work for querying jmx names too, like say > > you wanted > > to see all of hte jboss.system domains & components, you might be able to > > use "jboss.system.*:*" > > > > --jason > > > > > > _______________________________________________ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
