I just finished commiting this. I was unable to change the 'SingleJBoss' or the 'JMImplementation' domains, so I left them as they were. I don't know where the later even gets set. I tried changing SingleJBoss, but it is not as straight forward as the others I changed.
Currently the default build has the follwing domains: JMImplementation SingleJBoss jboss.j2ee jboss.jca jboss.jmx jboss.mq jboss.mq.destination jboss.security jboss.system jboss.system.classloader jboss.web jboss Where everything that did not fit into a specific domain went into jboss. It was a bit trickier than I had expected to make the change, as some compoinents did not check to make sure they had valid references to objects and throw some rather unhelpful exceptions. I have added some more detail to some of those areas to help avoid this in the future. I am still running into cluster related exceptions as well as some strange Remote and RMI exceptions... not really sure why... don't think they are related to the domain name change though. Components (like the Axis stuff) which are not part of the default tests may need a little help, though I really tried to update all names so it might just work. Happy new year. --jason -----Original Message----- From: Bill Burke [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 12, 2001 2:21 PM To: Jason Dillon; [EMAIL PROTECTED] Subject: RE: [JBoss-dev] more jmx domain structure 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
