Hello,

I am using Hibernate and EJB3 (with JBOSS AS) in three tier environment (Eclipse RCP client).

I would like to have some advice about dealing with lazy object on the client tier. I am sure expert like you have tricks about it :-)

Is DTO is out of date? Are there other solutions to have loosely coupling?


Thanks,

Regards,

Lazy loading can have issues in case of an object being accessed across multiple requets, as generally a transaction is inside a request, so any objects with lazily loaded children will throw exception : LazyInitializaionException: Owning session was closed.


Regards,
Jitendra

Thank you for your reply.

To avoid lazyInitialisationException on the client tier what is the procedure to follow ?
Using DTOs ? or are there better solution to reduce coupling and maintenance costs ?

Regards,

Well in our project we are planning on using entity caching in a big way as its going to be a huge clustered environment.

Depends on the size of your app, if its a small app then you can altogether skip lazy loading.

I do not have knowledge of DTO.

*Please do rate if it helps to solve your problem*

Regards,
Jitendra

Ok.
My app is quite large. About 100 entities in a clustered environment.
So I can not skip lazy loading on the business tier but in presentation layer I think I am obliged to skip lazy object due to different VM for client environment and to avoid LazyInitializationException.

My problem is how to manage this with loosely coupling.
The problem with DTO is to duplicate POJOs (without hibernate annotations) and consequently increase effort to maintain system.


Regards,