Thank you for the tip. persist and flush are done in different stateful session beans assembled in the same EAR. Unfortunately, the blog entry talks about TopLink specifics. Since we are an ISV we must write an EAR that is NOT TopLink specific. So is your tip mandatory by the spec, or is it only mandatory by TopLink?
Thanks
Markus
-----Original Message-----
From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
Sent: Dienstag, 24. Juni 2008 15:58
To: users_at_glassfish.dev.java.net
Subject: Re: GlassFish v2 Entity Cache problems
Hello Markus,
I'm not sure if you are doing the persist in a separate application from the find, but if its the same one, you have to be sure to set all bidirectional relationships. If not, you will get problems such as this where the cache does not reflect what is in the database - this is required by the JPA specification.
TopLink Essentails has issolated and shared caches which you can configure to meet your usage needs. I'd strongly recommend you read Wonseok's blog on the issue at
http://weblogs.java.net/blog/guruwons/archive/2006/09/understanding_t_1.html
Regards,
Chris
[Message sent by forum member 'chris_delahunt' (chris_delahunt)]
http://forums.java.net/jive/thread.jspa?messageID=282238
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net