Hi Marc > actually (ok you are right he was looking in the wrong place) I think that > using the MEJB for JMX access... well... why not?
Yes, you can but I don't think it is a good idea. I am currently talking with Hirom about the JBoss management tool and somehow we figured out that with JSR-77 you can't manage a J2EE server well except that you can start/stop existing components and find statistics about their performance. So any creation of new components (datasources, deployment -> JSR-88 etc.) or the changes of the current configuration is not supported by JSR-77. The change of the configuration can be added by vendor-specific attributes/ methods. I also think the the creation of new components can be added by vendor-specific components (under J2EEServer a components called JBossService). Today I will start added the first JBoss-specific component (SARModule, MBean) to the JSR-77 implementation. Let's see how this goes. > dude it will become the standard JMX access in a secure and transaction > fashion. Claudio got the secure part right... he missed the transactional > part and was pulling a jasonism.. "i don't get it? I rip it!"... I (respectfully) disagree, Sir. I think an Adaptor / Connector (like EJB or Juha's Adaptor/Connectors) are the correct way because MEJB is missing the createMBean() and the unregisterMBean() methods. > ok look, go walk the dog, make love to the wife as you are leaving for a > week and take care, > > Claudio, based on the clues we have, is partially right, Yes, he is, no argument here. See ya - Andy _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
