Hi,

I have class which contains a map that should always be loaded and present, also when the object is detached and passed to the web-tier. Therefore I added lazy="false" and fetch="join" to the <map> element in the mapping file.

This approach works if I query the object, and then detach it (i.e. close the session).

Unfortunately it does not work when the object is loaded by id (session.load(class,id)) or retrieved by navigating an association. In this situation the lazy="false" is ignored and the map is not fetched from the database. In the end a LazyInitializationException gets thrown.

Current workaround is to use Hibernate.initalize() in the DAO, but, due to the fact that the map in this class should alway be present and also provided in detached form, this approach is error prone (easy to forget the call) and probably slower than necessary.

Any ideas?

Thanks,
Alex

Sounds like you're doing all the right things. You could switch to using the Open Session In View pattern to avoid all that, but you don't have to.

All fetch="???" and lazy="???" attributes are at best hints. They apply only in certain circumstances, and can be overridden in most cases. Your data access layer will have to ensure that the map is initialized every time, unless you keep the session open until all necessary data has been retrieved.

Probably the class itself is being lazily-loaded. Set lazy="false" on the <class> element.