Hibernate version: 2.1.6
Jboss version: 3.2.6RC1


Hi all,
Forgive my newbie-ness...

I have my persistent classes deployed via a .har and everything is working fine.

So far, what I see as the usefulness of this deployment is that I can grab the session factory out of JNDI. Other than that what benefits do I get?

The reason I ask is that I tried reconfiguring hibernate with the MBean via the jmx-console, but I didn't see 'changes' that I applied via that affecting things.

For example, I'm using the bean shell servlet to play with hibernate so I wouldn't need to keep redeploying my 'test' code. I successfully grabbed the sesson factory via JNDI and loaded persisted data.

I changed the JNDI name from the jmx console, but then the bean shell script would not 'find' it under the new name. Isn't the point of the mbean stuff to enable runtime configuration?

Anyone out there willing to enlighten me?

Thanks,
Alex

Out of curiosity, does the runtime manipulation work for changing other Hibernate config attributes or is it just the JNDI name that didn't work?

the easiest to try was ShowSqlEnabled, initially it was true, and I see the sql calls.

I set it to false and still see the sql being logged.

So I'll assume it applies to all the properties (that are RW)

This might be still not working ... probably add a JIRA entry.

Yes, this is a known deficiency in the current implementation. There is currently discussion about what should be configurable via the MBean and what those changes mean. Most are not simple resetting of variables on the session factory, but instead imply rebuilding the session factory. And what's the best way to propogate that to other components, etc. Those are the types of things being discussed.

For the first release we really just wanted to focus on the har deployment and session management capabilities.

Thanks for the explanation....helps me know that I wasn't doing something stupid.