[
https://issues.apache.org/jira/browse/OPENJPA-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679699#action_12679699
]
Pinaki Poddar commented on OPENJPA-885:
---------------------------------------
> when I specified a change using a property, ex:
> openjpa.Compatibility=default(flushBeforeDetach=false),
When is 'when' exactly? After an EntityManagerFactory is obtained? After an
EntityManager is created?
Compatibility is singleton and non-dynamic. Changing its value later (say after
em is created) itself should be prohibited and if that is not happening that is
of concern.
Can you post some test case (and configuration artifacts) that demonstrates the
use case?
> when Compatibility is instantiated.
Plugin instantiation is lazy and on-demand -- unless you overwrite with
openjpa.InitializeEagerly.
> Is there an order specified for the providers?
I am assuming from the context 'providers' imply ProductDerivation. If that is
the case then yes. Follow the trails of ProductDerivation.getType().
> 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: 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.
