hi everyone,

how use a standalone application to test hibernate objets?

also, how to you test your hibernate objects?

Regards,
Paul

Junit

question is that all hibernate objects need to be deployed on application server. How can JUnit connect to objects on the server side?

Paul

What is the specific problem you are encountering ?

If you are writing code that uses hibernate to access the database, then test that code via a Junit test from the command line or IDE or whatever.

If you have hibernate code embedded in your server side code then test your server side code in exaclty the same manner as if you were coding manual SQL, whatever that is.

It almost sounds as if you are mixing business logic and persitence code layers.

THe persistence layer should be completely separate from the business logic layer, and should be capabable of being tested in a completely stand alone environment e.g. Junit test suites

I think this is an architecture question, not a hibernate question.

Not sure if this fits your development model, but we are using Hibernate through Spring and it is working very very well. Configuration of the Hibernate session works almost the same way in JUnit as it does in our web container. Spring provides great support for both Hibernate (Session and Transaction management; Exception hierarchy) and JUnit (Transactional test cases, etc).

HTH,

Chris

We use Spring as well and the only thing different that we do for tests is to have a different version of the Spring applicationContext.xml file, with the test version using a JDBC URL to get the connections, as opposed to the live one using a datasource.

This jsut allows us to test the hibernate coe without having the app server running.

Paul Newport, cbredesen,

are you using the AOP Interceptor or the Hibernate Template...? Just wanna know the best of two.

Thanks.

Etienne.

We extend Spring's base Hibernate DAO, which provides the template for your calls into Hibernate (either via Callback or convenience methods). Our transactions are managed by the TransactionInterceptor (AOP) around the business classes and we also use the OpenSessionInViewFilter to defer the session close till the end of our servlet request.

The OSIV functionality is also present in our JUnit integration tests, but I had to do a little coding to get that to work.

If you are asking whether I'm doing programmatic or declarative transaction management, we are using declarative. We never manually begin or commit/rollback transactions. Happy happy.

HTH,

Chris

Hi Chris,

what need to be extends in the spring base Hibernate DAO?

Thanks.

Etienne.

Everything you need to know is here:

http://hibernate.bluemars.net/110.html

To answer your specific question, you simply make all your DAO's extend HibernateDaoSupport, and then configure those DAO's in Spring's applicationContext to have a reference to the configured Hibernate session (also configured very easily in Spring) and you're good to go. All the Hibernate functionality is available to your DAO through getHibernateTemplate(). You can use either the convenience methods (common CRUD stuff) or call execute() and implement a HibernateCallback() which gives you full access to Hibernate session.

Enjoy!