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.
|Summary||Allow makePersistent outside a transaction||Allow makePersistent and deletePersistent outside a transaction|
|Fix Version/s||JDO 3 maintenance release 2 (3.2) [ 12316653 ]|
|Field||Original Value||New Value|
|Component/s||specification [ 12311332 ]|
|Component/s||tck2 [ 11652 ]|