RE: [Hibernate-devel] JBoss MBean

[Urberg, J. <ju...@ve...>]

>> Now, is the best way to support multiple SessionFactories to allow
multiple instances of the MBean, or should a single MBean manage
all the factories? <<

I would think it would be much simpler to have on per factory.  In the case
of JBoss, the user could setup each factory with a seperate MBean entry in
the jboss.jcml file.

>> Can anyone think of any other issues/requirements? <<

How about reloading the mappings every time the mapping file changes?  JBoss
does something like this with EJB jars.  If you copy an EJB jar to the
deploy directory it will automatically undeploy the EJB and then deploy the
new EJB.  It would be cool not to have to bounce the server each time a
mapping changed.

Another cool feature (though probably app server specific) would be the
ability to include the mapping with the EJB jar file.

>> P.S. I would like this MBean to be generic - useable by other JMX
applications apart from JBoss. (I think it is, anyway.)<<

JBoss adds the idea of a service life cycle and introduces it's own
interface for that purpose. The bean I created depends on that interface
plus some other JBoss support stuff.  JMX itself does not have a concept of
a life cycle or any ordering with the startup of different beans (such as a
JNDI service) which should make your attempt at a generic MBean interesting.

>> John, may I add your class to a new package cirrus.hibernate.jmx
in CVS?<<

Yes.