[jira] [Updated] (JDO-589) Allow makePersistent and deletePersistent outside a transaction

["Michael Bouschen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JDO-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Bouschen updated JDO-589:
---------------------------------
    Fix Version/s:     (was: JDO 3.2)

> Allow makePersistent and deletePersistent outside a transaction
> ---------------------------------------------------------------
>
>                 Key: JDO-589
>                 URL: https://issues.apache.org/jira/browse/JDO-589
>             Project: JDO
>          Issue Type: New Feature
>          Components: api, specification, tck
>    Affects Versions: JDO 2 maintenance release 1 (2.1)
>            Reporter: Craig L Russell
>            Priority: Major
>
> JPA allows users to call makePersistent outside a transaction, and then when beginning and committing a transaction, the instances are made persistent.
> This is similar to nontransactional dirty in which the managed instances can be modified outside a transaction and then the changes committed within a transaction.
> From the JPA spec, "When an EntityManager with an extended persistence context is used, the persist, remove, merge, and refresh operations may be called regardless of whether a transaction is active. The effects of these operations will be committed to the database when the extended persistence context is enlisted in a transaction and the transaction commits."
> This behavior should not be the default behavior (for backward compatibility reasons if not the principle of least surprise) so it should be under control of a PersistenceManager and PersistenceManagerFactory flag, perhaps NontransactionalNew.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)