[Jpox-issues] [JPOX JIRA] Commented: (NUCCORE-361) Unexpected flush for 1-to-1 + dependent="true" with optimistic lock

[Renato G. (JIRA) <web...@jp...>]

    [ http://www.datanucleus.org/servlet/jira/browse/NUCCORE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951#action_16951 ] 

Renato Garcia commented on NUCCORE-361:
---------------------------------------

1 - Testcase for "Transient instances cant be deleted"
I've included a new test scenario testNullifyNonPersistent1to1Relation using the existing DependentTestField, which reproduces the problem described. (DependentFieldTest-patch.txt)

2 - Unit Test
I ran a "mvn clean test" for the aggregator project test.maven2.parent(This is probably the "strange way" ;) Didn't know about the run_tests.sh script). I've noticed that ApplicationIdentityTest will fail using this "aggregator approach" with a "Unique constraint violation", probably other stuff won't work either.

So, I found the run_tests.sh script,  and I've ran the tests again using it.
The NEW results(test-result.zip) are attached along with the build output(testrun.out.zip). It already includes the new scenario above.

Please, could you check if they look alright now?(There are errors yet, but I assume they are already known). 

3 - TCK
I'm still trying to figure it out what I did wrong. I've run the tests using the 2.3-ea branch, I had to modify the project.xml to point to 2.0.0-SNAPSHOT version and force the "eb" version into the repo, by replacing jdo2-api-2.3-ea.jar. 

> Unexpected flush for 1-to-1 + dependent="true" with optimistic lock 
> --------------------------------------------------------------------
>
>                 Key: NUCCORE-361
>                 URL: http://www.datanucleus.org/servlet/jira/browse/NUCCORE-361
>             Project: DataNucleus Core
>          Issue Type: Bug
>          Components: JDO
>    Affects Versions: 1.1.5, 2.0.0.m1
>            Reporter: Renato Garcia
>         Attachments: DependentFieldTest-patch.txt, patch.txt, TCK-after.zip, TCK-before.zip, unit-test-result.zip
>
>
> A flush during causes problem to optimistic lock. See fourm details.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.datanucleus.org/servlet/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira