you mean PB.invalidate( new Identity( x )); // ?? j�rgen
Hi J�rgen, This looks like a cache synchronization problem. If you were using ODMG API, caches are synchronized automatically on transaction commits. If you are using PersistenceBroker API you have to do this explicitely. If you have updated an Object x you must call PB.ivalidate(x) to achieve proper synchronization. cheers, Thomas > -----Urspr�ngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:Jurgen.Richtsfeld@;tp-soft.com] > Gesendet: Dienstag, 12. November 2002 15:18 > An: [EMAIL PROTECTED] > Betreff: question belonging caches in client/server > > > hi! > we developed an application, that contains of a web-based part and an > application based part (via java webstart). now i have a problem with > synchronization. when i update objects in the webstart > application, and > commit my changes to the database (and the changes are done), the > web-based part of the application doesn't get the updated > objects until i > restart tomcat (version 4.0.3, OjbServlet). this doesn't > happen with newly > created objects. i viewed the code and didn't find a client > side cache. > the web-based application acts as a ojb-client, that is > currently on the > same machine. does anyone have an idea, what causes my trouble? > > thanx for help. > > juergen > > -- > To unsubscribe, e-mail: > <mailto:ojb-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: > <mailto:ojb-user-help@;jakarta.apache.org> > > -- To unsubscribe, e-mail: <mailto:ojb-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:ojb-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org>
