[Opensource] Forcing a DBObject to read from database instead of cache?

[Corey Snipes]

I'm running my Expresso app in one JVM, and a jobhandler in another JVM.  One of
my jobs needs to do some things with User() objects.  The behavior that I'm
seeing is this:

 - User is modified in the app, local references are notified that
   the object has been updated, and the cached objects behave
   correctly.

 - The jobhandler (separate JVM) has a cached User object, but doesn't
   know that it has changed, so uses old/outdated data for this user.

That's not ideal, but I can work with it if there's a method for forcing the
User object to read from the database.  But I'm not finding one that I can use.
There are a few in DBObject like removeFromCache() and setStatus("UPDATED")
which might be a reasonable hack, but they're all protected and my classes can't
see them.


Help...?  What am I missing?


-  Corey Snipes
   Programmer
   Seurat Company
   www.seurat.com
   P: +1-303-448-4800
   F: +1-303-448-4883