If by 'things' you mean concepts then yes, they are different things, but they are not exclusive of each other.
An MBean is simply a management interface for the underlying object. The interface has been registered with a lookup facility (MBeanServer derivative). The object itself can be anything: POJO, EJB, etc. Sometimes the object itself provides the management code, sometimes it delegates that code to a separate object (for instance, a 'manager' object). I just recently looked at a document that described this better, but I can't seem to locate it again. *drat* Therefore, what I am referring to is an EJB that has registered itself as an MBean. If for instance, you had a small pool of stateful EJBs, you could monitor to see how many were in a certain state (like checking user activity across the application), or even allow you to reset that state. Obviously altering the lifetime of the EJB through the management interface would a bad thing, since you would be stepping the EJB containers toes, while wearing wooden shoes. Now, with JBoss services (which AFAIK, must be an MBean), there is a separate descriptor stating when these services are started up and in what order. I am guessing that these should not be coded as EJBs, since something other than the EJB container is controlling their lifetime. I hope this is somewhat clear, I think I even confused myself :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886017#3886017 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886017 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
