You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Rick Curtis (JIRA)" <ji...@apache.org> on 2010/10/11 18:33:33 UTC

[jira] Commented: (OPENJPA-1705) Update migration section from 2.0.x -> 2.1.x in user manual to document eager cache initialization

    [ https://issues.apache.org/jira/browse/OPENJPA-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919890#action_12919890 ] 

Rick Curtis commented on OPENJPA-1705:
--------------------------------------

OPENJPA-1692 backed out[1] eagerly initializing the cache due to some internal test failures. This JIRA should be used to address this eager init problem and also documentation.

[1] Rev. 961008 and 961510

> Update migration section from 2.0.x -> 2.1.x in user manual to document eager cache initialization
> --------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-1705
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1705
>             Project: OpenJPA
>          Issue Type: Improvement
>    Affects Versions: 2.1.0
>            Reporter: Rick Curtis
>            Assignee: Rick Curtis
>
> We need to document that in 2.1.x we will eagerly initialize a configured cache, even if it is never used. This function was changed in OPENJPA-1646.

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