You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Pinaki Poddar (JIRA)" <ji...@apache.org> on 2008/08/26 23:20:44 UTC

[jira] Updated: (OPENJPA-620) OpenJPA configuration setting that guarantees that once the EMF is created, it will be fully-configured

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

Pinaki Poddar updated OPENJPA-620:
----------------------------------

    Attachment: openjpa-620.patch.1.txt

This patch introduces a new boolean property openjpa.InitializeEagerly to force eager initialization of persistent classes + database resources.

Given the feature "would be useful for early detection of errors", I have added fail-fast behavior on loading persistent types retaining the existing behavior as default. Only the new openjpa.InitializeEagerly triggers metadata resolution in a fail-fast way (rather than ignoring empty list or persistent classes or unloadable classes).   


> OpenJPA configuration setting that guarantees that once the EMF is created, it will be fully-configured
> -------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-620
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-620
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: kernel
>    Affects Versions: 0.9.0, 0.9.6, 0.9.7, 1.0.0, 1.0.1, 1.0.2, 1.1.0
>            Reporter: Srinivasa
>            Priority: Minor
>         Attachments: openjpa-620.patch.1.txt
>
>
> Lot of the processing - like the loading of configured persistent types, processing the metadata for the registered classes happens at the time of creating an EM or even later when the metadata resolution is needed. Having a configuration where the obtaining of the EMF does all this processing would be useful for early detection of errors, and for managed environments where this could be done as a part of an application deploy step rather than happening at runtime. 

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