Do we really need DAO layer when using Hibenrate objects

hjshi · **Joined:** Wed Jun 09, 2004 2:49 pm **Posts:** 25

When using Hibernate ORM, I don't feel I need another DAO layer.
Just wondering how many of you share my feeling.

j2eeprofessional · **Joined:** Thu Aug 24, 2006 2:16 am **Posts:** 4

your hibernate code would come in ur DAO layer itself...why would u need another one ?

hjshi · **Joined:** Wed Jun 09, 2004 2:49 pm **Posts:** 25

Look at Spring/Hibernate integration example and you will know my question.

damnhandy · **Posted:** Fri Sep 08, 2006 11:55 am

I agree. I think the DAO pattern can be an unnecessary layer to your application when using Hibernate or other ORM tool. If your in a J2EE environment, your SessionBean can act as a DAO layer. Hell, some JEE 5 examples do exacly that.

However, it can be useful if you think you could be changing persistence architechures and the means to access you data will change as a result. Additionally, A DAO is MUCH easier to test than a SessionBean as it does not require you test it in-container. I still use DAOs for that reason alone, otherwise its just extra code in your app.