RE: [Hibernate-devel] JBoss MBean

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

>> > How about reloading the mappings every time the mapping file
changes?...<
What would be involved in this? ie. how would we know the mapping file
changed, assuming we load it using getResourceAsStream()? <<

I think you'd have to get the file's timestamp and then poll it at regular
intervals to see if it changed.  I wanted to do that with the Hibernate
MBean I created but didn't have the time.

>> That is the recommended way to deploy mappings, as far as I'm concerned.
So we would definately allow this. <<

Hmm.  I've been assuming the use of one big mapping file.  I supposed if you
put each class mapping in a seperate file, that would take care of it.  It
would also make the part about checking for the mapping file changing more
difficult.

>>As far as I can tell the only JBoss-specific thing in your MBean is the
startService() / stopService() methods from the inherited JBossServiceMBean
interface. (Since JBoss has a compatible license, we should be able to just
distribute that interface along with Hibernate.) Then, as far as any other
JMX client is concerned startService() / stopService() are just any old
management operations that could be invoked by the user (rather than by
the container in the case of JBoss).<<

How would the service get started in non-JBoss containers?

Regards,
John Urberg