I see.
Thanks a lot for explaining.
Just a side question: This means that all SessionBean programmers must know all internals of all entities. I mean, how shall I know from a precompiled entity provided by a third party, what bidirectional releationships it has?
Thanks
Markus
-----Original Message-----
From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
Sent: Dienstag, 24. Juni 2008 16:35
To: users_at_glassfish.dev.java.net
Subject: Re: RE: Re: GlassFish v2 Entity Cache problems
A refresh would defeat the purpose of caching at the Persistence Unit level. Caching Entities at the PU level provides very large performance benefits to the majority of applications.
A well thought out locking/refreshing and caching strategy needs to be implemented to handle any concurrent modifications by other threads or 3rd party software.
The specification does require that developers set both sides of a bi-directional relationship when updating relationships.
--Gordon
[Message sent by forum member 'gyorke' (gyorke)]
http://forums.java.net/jive/thread.jspa?messageID=282249
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net