[forge-issues] [JBoss JIRA] (FORGE-813) Implement a strategy to fix the open session in view problem in the generated REST resources

Sun Mar 17 16:28:41 EDT 2013

     [ https://issues.jboss.org/browse/FORGE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vineet Reynolds updated FORGE-813:
----------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/forge/core/pull/299

The JOIN FETCH expressions ensure that immediate collections are fetched. This fits in well, with the upcoming changes for FORGE-606, where the first immediate properties of an object are serialized, thus avoiding the open-session in view.

Collections at a deeper level in the related entities may be fetched, depending on the EAGER/LAZY fetchType values on the nested collections.

Also replaced Seam Render usage with FreeMarker.

> Implement a strategy to fix the open session in view problem in the generated REST resources
> --------------------------------------------------------------------------------------------
>
>                 Key: FORGE-813
>                 URL: https://issues.jboss.org/browse/FORGE-813
>             Project: Forge
>          Issue Type: Feature Request
>          Components: Java EE APIs
>            Reporter: Vineet Reynolds
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira