Design issue (POJO and DTO/VO)

manjusingh · **Joined:** Thu Aug 03, 2006 11:18 pm **Posts:** 5

I am using struts -> Java Object (business Tier, e.g. Spring) -> Hibernate.

General practice for sendnig data to DAO is through DTO/VO for coarse grain data transfer. With hibernate we have POJO which is same as DTO. Is it good practice to use POJO for data transfer from presentation tier to Hibernate DAO, that means web tier will instantiate the POJO class, populate the POJO object and send it to DAO for persistence.
Or, shall we create separate DTO and separate POJO class ???

tenwit · **Joined:** Thu Dec 23, 2004 9:08 pm **Posts:** 2008

I use the same classes for both. I can't think of a reason not to. If there's a problem due to CGLib enhancements, etc., you can always copy the fields from a DAO object into another object of the same class, effectively making it a DTO object.

hari.manivannan · **Joined:** Tue Nov 29, 2005 11:20 am **Posts:** 9

On the same lines, I have another question. What about the return route i.e from DAO to webTier. Is it recommended to bring over the hibernate POJOs or to copy over the values to similar POJO and send it back for UI display, so that we can work in a detached mode?

Can someone give best practices and design guidelines on the same.

~H