[
https://issues.apache.org/jira/browse/OPENJPA-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980008#action_12980008
]
Cyrille Charron commented on OPENJPA-1921:
------------------------------------------
Oups, i didn't see the setter error.
Thanks a lot !
The suggestion of Mickael Dick resolved the problem.
Changing the getter "class Person { public Integer getVersion(); ... }" into
"class Person { public int getVersion(); ... }" resolved the problem.
I can even keep the setter "class Person { protected void setVersion(Integer
version); ... }" which still works.
> Persist detached object error when using PROPERTY access instead of FIELD
> access
> --------------------------------------------------------------------------------
>
> Key: OPENJPA-1921
> URL: https://issues.apache.org/jira/browse/OPENJPA-1921
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.0.1
> Environment: Windows XP, JUnit test under Eclipse.
> Reporter: Cyrille Charron
> Attachments: FamilyModel.zip, HibernateTest.zip, OpenJPA-bug.txt
>
>
> When changing my orm.xml file to have access="PROPERTY" instead of
> access="FIELD", my JUnit test fails with an EntityExistsException.
> Id of my entities are not generated, but set manually.
> I join 2 zip files of the Eclipse test project (1 for the entities, 1 for the
> test under OpenEjb), and the stdout file with the error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
