[
https://issues.apache.org/jira/browse/OPENJPA-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dianne Richards updated OPENJPA-885:
------------------------------------
Attachment: CompatibilityProblemPatch.txt
I'm attaching the CompatibilityProblemPatch file. This contains 2 test cases.
The first one, TestCompatibilityChanges, show that things are working fine.
The secondOne, TestCompatibilityProblem, shows the problem. In the second one,
I've added a property change to the setUp call. This apparently ends up passing
the property in on the createEntityManagerFactory().
Also in this patch are 2 code changes. The Compatibility class has several new
instance variables with associated setter/getter methods. The
PersistenceProductDerivation class has calls to the setter methods to change
the default values for openjpa.
So, to repeat what is happening, the PPD changes are working correctly
initially, as seen in the TestCompatibilityChanges test case. But, when a
change to Compatibility is specified on the createEMF(), these changes are lost
because the entire Compatibility object is lost when the _value variable is set
to null. I realize the this is a singleton. However, this property seems to be
a special case because iterative changes can be made to it.
> Support clear methods on EntityManager, including new CascadeType.CLEAR
> ------------------------------------------------------------------------
>
> Key: OPENJPA-885
> URL: https://issues.apache.org/jira/browse/OPENJPA-885
> Project: OpenJPA
> Issue Type: Sub-task
> Affects Versions: 2.0.0
> Reporter: Dianne Richards
> Assignee: Dianne Richards
> Fix For: 2.0.0
>
> Attachments: CompatibilityProblemPatch.txt, patch.txt
>
>
> Support the 2.0 new EntityManager clear() methods. Also support the new
> CascadeType.CLEAR.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
