Hi Craig,

I have some questions wrt lifecycle transitions. Please see below:

1) Does pm.detachCopy(persistent-nontransactional-dirty) throw an exception?

2) How does a non-transactional-dirty instance transition at commit time
when DetachAllOnCommit is true?

3) Does pm.makeTransient(persistent-nontransactional-dirty) throw an
exception?

4) At commit time a non-transactional-dirty instance transitions to
hollow when DetachAllOnCommit is false and RestoreValues is false. As a
consequence, the changes made before begin are lost. Is this intentional?

5) At commit time flushing a non-transactional-dirty instance may result
in a concurrency conflict for optimistic transactions because the spec
requires a version check. For datastore transactions commit would be
successful. Non-transactional-dirty seems to be the only state where
both transaction types have different semantics wrt concurreny
conflicts. Is this intentional?

Regards,
Michael
--
-------------------------------------------------------------------
Michael Watzek                  Tech@Spree Engineering GmbH
mailto:mwa.tech@spree.de        Buelowstr. 66
Tel.:  ++49/30/235 520 36       10783 Berlin - Germany
Fax.:  ++49/30/217 520 12       http://www.spree.de/
-------------------------------------------------------------------

[ Post a follow-up to this message ]

[ Post a follow-up to this message ]