openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <>
Subject [jira] Updated: (OPENJPA-1328) Move cacheable class configuration to ClassMetaData
Date Tue, 02 Feb 2010 23:55:18 GMT


Michael Dick updated OPENJPA-1328:

    Fix Version/s: 1.0.4

> Move cacheable class configuration to ClassMetaData
> ---------------------------------------------------
>                 Key: OPENJPA-1328
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: datacache
>    Affects Versions: 1.2.0, 1.2.1
>            Reporter: Jody Grassel
>            Assignee: Michael Dick
>             Fix For: 1.0.4, 1.2.2, 1.3.0, 2.0.0
>         Attachments: OpenJPA_1.2.x_OJ1328.patch
> I'm proposing to move the cacheable class configuration processing from the datacache
classes to ClassMetaData.  The feature, introduced in OPENJPA-1045, effectively works by returning
null for ClassMetaData.getDataCacheName(), where classes which should not be cached return
null, otherwise the name of the datacache they may be cached by is returned.  
> THe problem is that some third party datacache plugins are not reentrant, and the existing
ClassMetaData.isCacheable() makes use of the method call getRepository().getConfiguration().getDataCacheManagerInstance().
 This invokes the initialization of the datacache, which may result in further initialization/copying
of CMD objects, which reenter the isCacheable() method.  If a third party datacache plugin
is not reentrant safe, this can cause a failure in the form of Exceptions or hung threads.

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

View raw message