Hi,
I'm encoutering that exact bug :
https://issues.apache.org/jira/browse/OPENJPA-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619733
#action_12619733
Apparently, it is stil open since August 2008. Any news or status
about that ?
Any workaround ?
I iunderstand I can't assign value to @Id where strategy is set to
generated, that make sense, but the serialisation/deserialisation
process from client to server did it !
This is a mandatory step, as the deserialisation has to set that id
value, otherwise, how would that instance been recognized as not new
without an id ?
I'm using openjpa-1.2.2-SNAPSHOT-r422266:809017