db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Braeuchi (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (OJB-35) Refresh on ClassDescriptor causes a new instance to be cached
Date Mon, 06 Jun 2005 06:06:40 GMT
     [ http://issues.apache.org/jira/browse/OJB-35?page=all ]
Jakob Braeuchi resolved OJB-35:

    Resolution: Duplicate

duplicate of ojb-34

> Refresh on ClassDescriptor causes a new instance to be cached
> -------------------------------------------------------------
>          Key: OJB-35
>          URL: http://issues.apache.org/jira/browse/OJB-35
>      Project: OJB
>         Type: Bug
>   Components: PB-API
>     Versions: 1.0.x CVS, 1.1 CVS
>     Reporter: Andrew Clute

> When a ClassDescriptor has the refresh attribute set, a new instance of that object is
placed into the localCache.
> This stems from the the fact that PersistenceBrokerImpl#refreshInstance() calls PersistenceBrokerImpl#getDBObject().
This has the unintended consequence of the new  object restored being placed into the localCache,
and thus overwriting the previous Cached versions reference.
> The fix is simple, as a new method called getPlainDBObject is introduced that only does
the retrieval, and getDBObject is refactored to use getPlainDbObject. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org

View raw message