[
https://issues.apache.org/jira/browse/JDO-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525964
]
Craig Russell commented on JDO-452:
-----------------------------------
> I see that JDOEntityTransaction is not defined,
The JDO Transaction is already a strict superset of EntityTransaction. To
provide for a future EntityTransaction that includes more methods than are
available in JDO Transaction, we could create a JDOEntityTransaction. But we
could as easily add the new method directly to JDO Transaction.
> but the following should be good enough:
> ((JDOEntityManager)em).currentTransaction().setOptimistic(false);
I'm not clear which case this is. If you need to setOptimistic, you need either
a PersistenceManager or a JDOEntityManager from which to get the
currentTransaction. If all you have is an EntityManager (that doesn't implement
PersistenceManager or JDOEntityManager), you can't cast it. If you have a
JDOEntityManager, you don't need to cast it.
>Do we need a method like em.getDelegate() but in the other direction, to get
>an EntityManager from a PersistenceManager proxy?
I've changed the return type of
JDOEntityManagerFactory.getPersistenceManagerProxy to return JDOEntityManager.
Is this enough?
> Provide interfaces that extend both JDO and JPA
> -----------------------------------------------
>
> Key: JDO-452
> URL: https://issues.apache.org/jira/browse/JDO-452
> Project: JDO
> Issue Type: New Feature
> Components: api2
> Affects Versions: JDO 2 final
> Reporter: Michelle Caisse
> Assignee: Craig Russell
> Fix For: JDO 2 maintenance release 1
>
> Attachments: jdo-452.patch, jdo-452.patch
>
>
> Provide interfaces that extend both JDO and JPA in order to make it easier to
> migrate applications from JDO to JPA.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
