Hi Eric.
You are right. I replaced OpenJPA 2.0.1 with 2.1.0-snapshot and warning
message is gone.
Thank you.
Best regards
Georgi
Eric Charles wrote:
Hi,
May be related to this thread?
http://markmail.org/message/u3flgv3yux7djg6i
Tks,
Eric
On 27/09/2010 13:53, Georgi Naplatanov wrote:
Hel
At least someone can tell me if im going right that the ID had to be set?
--
View this message in context:
http://openjpa.208410.n2.nabble.com/OneToMany-list-object-problem-with-IDENTITY-keys-tp5583159p5584026.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
Heiko,
Thanks for following up so quickly. I put together a quick test and wasn't
able to produce the same result. I was just about to type up an email
asking for more info. I'm glad to hear you were able to work around the
issue with a simple change.
I agree that having the exception surfaced
Hi,
I am able to see the problem you reported. Note that em.merge(entity)
returns a managed object and Verfahrenstatus gets merged internally/implicitly
by OpenJPA along with Verfahrendokument. It appears that OpenJPA fail to set
the
Id for Verfahrenstatus after merge. I will investigate
Hi,
As mentioned in the email below, em.merge() returns a managed object.
Since Verfahrenstatus gets merged internally by OpenJPA, not explicitly by the
API call, the application can not get the merged object for Verfahrenstatus
immediately after the em.merge call. The workaround is to c
