The cache implementation is configurable.  OJB can be configured to have a static 
cache that holds the objects loaded from the db for all time ObjectCacheDefaultImpl, a 
cache that is limited in scope to a single transaction (actually from the time you get 
a broker from the pool to the time you return it) ObjectCachePerBrokerImpl, or no 
caching via ObjectCacheEmptyImpl.  There's even some more implementations I'm not sure 
what do.

If you were seeing changes made through SQL not reflected in queries your 
OJB.properties is probably configured with ObjectCacheDefaultImpl.

-----Original Message-----
From: Joe Germuska [mailto:[EMAIL PROTECTED]
Sent: Sunday, January 25, 2004 10:29 AM
To: OJB Users List
Subject: Re: Choosing a cache implementation


>
>This shouldn't be a big problem because "per-broker" cache clears its
>cache after each PB.close/PB.commit/PB.rollback event, thus at the
>latest after PB.close/PB create sequence the "new" data was used.

Wow, that clears things up; I had some idea that OJB had a 
"system-wide" cache of some sort, but now  I think I understand that 
the cache is just within a transaction context (or transaction-ish) 
to avoid cyclical object calls and such.

But wait... I know I've had situations where I've made database 
changes with SQL and don't see them in the JVM runtime until I 
restart the application.  Well, I think I know that.  I always 
thought that was related to the caching.

Are there two different aspects of object caching?  Am I just 
confused?  Maybe I need to run a few more tests.

Armin, I really appreciate your help.  Thanks

        Joe


-- 
Joe Germuska            
[EMAIL PROTECTED]  
http://blog.germuska.com    
       "Imagine if every Thursday your shoes exploded if you tied them 
the usual way.  This happens to us all the time with computers, and 
nobody thinks of complaining."
             -- Jef Raskin

---------------------------------------------------------------------
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]

Reply via email to