Implement a strategy to fix the open session in view problem in the generated REST resources

The generated REST resources for objects with 1:M and M:M relations, require eager fetching to be enabled on the related JPA entities, to bypass the open-session-in-view problem.

The generated REST resources should not require the entities themselves to use eager fetching by default. It would be better to use specialized JPQL queries to achieve this.

Or for that matter, use a combination of specialized JPQL queries that limit the objects being retrieved (say, one-level deep) and custom serializers that can operate on this partial object graph.