Uh, actually, from my experience, objects updated via OJB, they were NOT updated in the cache. It appears the starter of this thread had the same issue. I had to completely turn off caching to get my updates to appear on the client side...
-Clay Armin Waibel wrote: > Think both is ok. ObjectCacheDefaultImpl is > a simple global cache which does not remove > expired objects (no decay time support for objects) or does refresh > periodically. > But if objects were changed in OJB > these changes reflected in cache. If objects > outside of OJB were changed you are doomed ;-). > You can easily write your own more > sophisticated ObjectCache implementation. > see > http://db.apache.org/ojb/objectcache.html > Oleg is currently refactoring the cache > package, so rc5 will offer much more > flexibility . > > regards, > Armin > > >>>BTW, I have set autoCommit="0" in repository_database.xml, I think >>>autoCommit is not very good in some situations? >>> >>>Thanks for your any hints and help! >>> >>>linuxman >>> >>>_________________________________________________________________ >>>免费下载 MSN Explorer: http://explorer.msn.com/lccn/ >>> >> >>--------------------------------------------------------------------- >> >>>To unsubscribe, e-mail: [EMAIL PROTECTED] >>>For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >>> >> >> >> >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
