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/08/19 00:01:22 UTC
[jira] Resolved: (OPENJPA-1769) Broker getObjectId(...) doesn't
return a proper object id for an Entity that is detached and has no
DetachedStateManager
[ https://issues.apache.org/jira/browse/OPENJPA-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Curtis resolved OPENJPA-1769.
----------------------------------
Resolution: Fixed
Committed revision 986963 to trunk.
> Broker getObjectId(...) doesn't return a proper object id for an Entity that is detached and has no DetachedStateManager
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1769
> URL: https://issues.apache.org/jira/browse/OPENJPA-1769
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 2.0.0, 2.1.0
> Reporter: Rick Curtis
> Assignee: Rick Curtis
> Priority: Minor
> Fix For: 2.1.0
>
>
> While investigating test failures for OPENJPA-1469 I found that the test org.apache.openjpa.persistence.detachment.TestDetachNoStateField failed due to a bug in BrokerImpl.getObjectId().
> The problem with the TestDetachNoStateField is that when we tried to save the relationship from a managed entity to a detached(with no DSM) we failed to get the oid of the detached Entity. In turn we weren't updating the cache properly. I added a new test case to test only the failing part of the broker.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.