False alarm:
http://weblogs.java.net/blog/guruwons/archive/2006/09/understanding_t_1.html
Sorry but as C/S developer I expected that the refresh behavior IS the
default not a feature.
Thanks.
Regards.
-----Mensaje original-----
De: Marina.Vatkina_at_Sun.COM [mailto:Marina.Vatkina_at_Sun.COM]
Enviado el: Martes, 12 de Febrero de 2008 02:08 p.m.
Para: persistence_at_glassfish.dev.java.net
Asunto: Re: I think I found a bug
This is not a bug, but a documented behavior of TopLink Essentials. Search
GlassFish forum for caching or google for Wonseok blog and you'll find the
answers.
thanks,
-marina
Sergio Samayoa wrote:
> Hi.
>
> I'm experimenting with toplink with desktop applications and I think I
found
> a bug.
>
> Top link doesn't sees the changes make by other applications.
>
> This is the scenario:
>
> 1. TopLink application ("TLA" from here) starts and fetch some entities.
> 2. Another application ("OA" from here) access the same database and
updates
> one record then commits.
> 3. TLA's clears its persistence context (EntityManager.clear()) then
fetches
> again the records. The updated record stills as if weren't updated.
>
> I'm pretty sure that the record is updated in the database but top link is
> using existing entity instance without updating with the new data.
>
> My environment:
>
> Top Link 2.0-58g
> JDK 1.6.0_03
> Windows XP SP2
>
> At this moment this bug is a stopper for multi-user desktop applications.
>
> Where can I report it?
>
> Regards.
>
>