Yeah - I've reviewed that package but it doesn't appear to solve the real issue. The getMessage() call in the OJBMessageResources class clears the cache of the MessageResources class. That's fine, but as soon as you return the value back up to MessageResources, it's going to put it on the cache again. So the next call into the getMessage() of the MessageResources class happens, it's going to 1) look onto it's cache and then 2) get the value off without ever going to the subclass. The problem here is that the messageResources class is maintaining a cache. Why not let the implementation actually control the cache? We end up having 2 caches with any approach...
Bill Siggelkow <[EMAIL PROTECTED]> wrote: http://sourceforge.net/project/showfiles.php?group_id=49385&package_id=76369 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------- Do you Yahoo!? Yahoo! Mail is new and improved - Check it out!
