You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Michael Dick (JIRA)" <ji...@apache.org> on 2008/07/31 22:26:33 UTC

[jira] Updated: (OPENJPA-647) Dynamic update to DataCacheTimeout property is not updated in the ClassMetadata

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

Michael Dick updated OPENJPA-647:
---------------------------------

    Fix Version/s: 1.2.0

> Dynamic update to DataCacheTimeout property is not updated in the ClassMetadata
> -------------------------------------------------------------------------------
>
>                 Key: OPENJPA-647
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-647
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: datacache
>    Affects Versions: 1.1.0
>         Environment: OpenJPA 1.1.0
> version id: openjpa-1.1.0-r422266:656510
> Apache svn revision: 422266:656510
> os.name: Windows XP
> os.version: 5.1
> os.arch: x86
> java.version: 1.6.0_05
> java.vendor: BEA Systems, Inc.
>            Reporter: Sandeep Shrivastava
>            Assignee: Pinaki Poddar
>             Fix For: 1.2.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The org.apache.openjpa.meta.ClassMetaData caches the value of the DataCacheTimeout when it is first accessed. On a subsequent update of the OpenJPAConfiguration's  property this cached value is not cleared and the ClassMetaData instances in the repository that have initialized the DataCacheTimeout from either the parent class or the global default continue to use the old value. We need to build smarts in this class so that the configuration cache can be cleared on an update and this property reflects true dynamic behaviour.

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