I have two applications connected to the same DB. For the first, data mostly goes in (think data entry). For the second, data comes out (think reporting). The first application is finished, and all POJO's amd HBMs used for persistence are in a seperate jar. If both apps use this jar, they must both have the same eager/lazy configuration. I want the data entry application to be totally lazy, and the reporting app to be totally eager. How do I get around this?

Perhaps using "entity-name" and having two mappings coexisting together?

You can define all the mappings as lazy and use the Criteria API, specifically the criteria.setFetchMode("alias", FetchMode.JOIN) and specific application methods to change this at runtime.

You can also override the configuration programatically at run time, like this:



This will be passed into the SessionFactory and will control the behavior for the application, as if it had been hard-coded into the mapping file. Although I haven't done it, you could probably do some looping code to do this en masse for the whole configuration.

--Jesse