I've been having trouble developing a testing scheme in our architecture with Hibernate.

We're using Hibernate inside of an EAR and loading the SessionFactory into JNDI at startup of the container. This works perfectly for our Struts web application. We use POJO's to map out our business logic and call them from Struts actions.

However, our problem lies in trying to use JUnit to test our POJO's outside of the EAR container. Since all of the POJO's rely on using JNDI to retrieve Hibernate from JNDI, Hibernate does not remote outside the container to the JUnit classes. WebLogic throws an exception with the POJO's try and access JNDI outside of the EAR container.

I'm interested to know what others do in this situation. I'm sure there are plenty of alternatives. Thoughts?

you should really have a look at the spring framework.

Spring provides different contexts (web, filesystem, etc...).

What we do with Junit is use the spring filesystem context. In struts actions we call the spring provided webcontext. Such contexts are made both by the same spring configuration file, thus you are testing the same POJOs and DAOs in different environments.


http://www.springframework.org

Hope it helps.