Hi,
my question is very simple.
below is my method.

public EmployeeDTO getEmployeeInfo( String userId ) throws PersistenceCriticalException {
EmployeeDTO employeeDTO = null;
try {
begin();
employeeDTO = ( EmployeeDTO ) getSession().get(EmployeeDTO.class, new Integer(userId));

commit();
} catch( Exception e ) {
throw new PersistenceCriticalException( e );
} finally {
close();
}
return employeeDTO;
}

after closing the session by close(); method.
i cant retrieve the employeeDTO's objects lazily.
if i set lazy="false" in mapping file I can view retrieve the data.

however, setting lazy="false" is hampering my performance.
is there any other way to retrieve the required information lazily after closing the session();

or is there any other method where i dont need to compromise on performance?

You'll always need an open session. So if the original session has been closed you have to open a new session and use Session.lock() to reassociate the original object with the new session.

Thanks buddy :)
but how can i carry my session object to UI or Domain layer. it wont be a good practice.

Ne ways, thanks for your reply.

This is a common problem and there are many different solutions to it. The main problem here is that your DAO is closing the session. This is usually considered an anti-pattern. Opening and closing sessions should usually be handled at some higher level that knows about the current "unit-of-work".

To begin with you should read http://www.hibernate.org/43.html

A lot of Hibernate users are using Spring which has builtin support for session handling. I have no experience with Spring myself, but it seems to be popular when using Hibernate in a web environment.