Hi Folks,

I am running JBoss 4.02 that's running a series of applications, each of which has its own .har file. During startup, jboss sets up the SessionFactory before any of my own code is seen. I'm trying to integrate hibernate annotations as well as lucene.

I need to know how to intercept or override the buildSessionFactory() method in org.jboss.hibernate.jmx.Hibernate so that I can use an AnnotationConfiguration instead of a Configuration to instantiate the SessionFactory. Any hints as to how to go about this without re-building jboss?

Thanks for any help.

-Greg

Hibernate version: 3.2 RC1

Mapping documents: N/A

Code between sessionFactory.openSession() and session.close(): N/A

Full stack trace of any exception that occurs: N/A

Name and version of the database you are using: Oracle 10.1

The generated SQL (show_sql=true): N/A

Debug level Hibernate log excerpt: DEBUG
2006-04-06 19:40:03,538 DEBUG [org.jboss.system.ServiceController] starting service jboss.har:service=BspCoreHibernate
2006-04-06 19:40:03,538 DEBUG [org.jboss.hibernate.jmx.Hibernate] Starting jboss.har:service=BspCoreHibernate
2006-04-06 19:40:03,538 DEBUG [org.jboss.hibernate.jmx.Hibernate] Hibernate MBean starting; org.jboss.hibernate.jmx.Hibernate@b02f33 [ServiceName=jboss.har:service=BspCoreHibernate, JNDI=java:/hibernate/BspSessionFactory]
2006-04-06 19:40:03,538 DEBUG [org.jboss.hibernate.jmx.Hibernate] Building SessionFactory; org.jboss.hibernate.jmx.Hibernate@b02f33 [ServiceName=jboss.har:service=BspCoreHibernate, JNDI=java:/hibernate/BspSessionFactory]
2006-04-06 19:40:03,618 INFO [org.hibernate.cfg.Environment] Hibernate 3.2 cr1

I figured out a method to resolve this ... I needed to brush up on my jboss admin skills. I created a custom MBean that looked like the existing HibernateMBean and called that from the hibernate-service.xml file. Updating my customized MBean allowed me to use my own AnnotationConfiguration so I could instantiate annotated classes.

alternatively you might want to use JBoss EJB3, this is all done for you and you can inject Sessions rather than EntityManagers if you want to

Thanks, we'll definitely do that once we migrate to that. In the meantime, it looks like what I have now will work for our current production deployment. Thanks,

-Greg