Hi Ilan,
As far as I can see, the fix checked in for JDO-514 should address the
issue you raised there. On line 229, we changed
transaction.setNontransactionalRead(true);
to
transaction.setNontransactionalWrite(true);
The original was probably a typo. Experimenting with this change in the
trunk, print statements show that transaction.getNontransactionalWrite()
returns true when there is no active transaction and current_state is
PERSISTENT_NONTRANSACTIONAL_DIRTY.
Can you take another look and see if there might be some other problem?
Thanks,
Michelle
Ilan Kirsh wrote:
Hi Michelle,
Thank you for the fixes.
It seems that all the challenges except one are solved now.
I still have a problem with StateTransitionsReturnedObjects.
As far as I can see, JDO-513 was fixed, but not JDO-514.
Thanks and regards,
Ilan
----- Original Message ----- From: "Michelle Caisse"
<[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, October 05, 2007 10:54 PM
Subject: Re: CHALLENGE
org.apache.jdo.tck.lifecycle.StateTransitionsReturnedObjects.java
Hi Ilan,
I've checked in changes for all the challenges to the 2.0.1 branch.
Please
let me know if there are any problems with the fixes.
-- Michelle
Ilan Kirsh wrote:
Challenge against JDO TCK 2.01:
http://issues.apache.org/jira/browse/JDO-513
http://issues.apache.org/jira/browse/JDO-514
Issues are not solved yet.
Ilan Kirsh, ObjectDB Software
