You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Patrick Linskey (JIRA)" <ji...@apache.org> on 2007/07/26 22:20:03 UTC

[jira] Created: (OPENJPA-297) Lazy loading must be ignored in certain unenhanced cases

Lazy loading must be ignored in certain unenhanced cases
--------------------------------------------------------

                 Key: OPENJPA-297
                 URL: https://issues.apache.org/jira/browse/OPENJPA-297
             Project: OpenJPA
          Issue Type: Sub-task
            Reporter: Patrick Linskey
             Fix For: 1.0.0


When using unenhanced classes, sometimes OpenJPA is unable to intercept field accesses, and therefore unable to do lazy loading of those fields prior to access. In these cases, we should eagerly load data that was marked as lazy.

This will happen in the following scenarios:

- all instances (user-created and OpenJPA-created) when using field access and redefinition is not available

- user-created instances (new instances) when using property access and redefinition is not available

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (OPENJPA-297) Lazy loading must be ignored in certain unenhanced cases

Posted by "Patrick Linskey (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/OPENJPA-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Linskey resolved OPENJPA-297.
-------------------------------------

    Resolution: Fixed

> Lazy loading must be ignored in certain unenhanced cases
> --------------------------------------------------------
>
>                 Key: OPENJPA-297
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-297
>             Project: OpenJPA
>          Issue Type: Sub-task
>            Reporter: Patrick Linskey
>             Fix For: 1.0.0
>
>
> When using unenhanced classes, sometimes OpenJPA is unable to intercept field accesses, and therefore unable to do lazy loading of those fields prior to access. In these cases, we should eagerly load data that was marked as lazy.
> This will happen in the following scenarios:
> - all instances (user-created and OpenJPA-created) when using field access and redefinition is not available
> - user-created instances (new instances) when using property access and redefinition is not available

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.