Rainer Klute wrote: ...
hmm, you can use non-distributed ObjectCache implementation, e.g. ObjectCachePerBrokerImpl. This supports circular references and avoid concurrent object modification by other threads/broker instances.
But you will loose all cached objects when broker was closed/rolled back.
Nevertheless, if you have a fast DB and a fast network between OJB and DB this should be ok.
I tried the ObjectCachePerBrokerImpl but unfortunately lost the circular references.
hmm, this implementation does support circular references. Think there is something going wrong in your app, e.g. different threads using same PB instance.
forthcoming OJB versions! I'll keep an eye on its development - but just not now.
Okay, folks, thanks for your time and effort and good luck with
Thanks for give it a try.
regards, Armin
Best regards Rainer Klute
Rainer Klute IT-Consulting GmbH Dipl.-Inform. Rainer Klute E-Mail: [EMAIL PROTECTED] K�rner Grund 24 Telefon: +49 172 2324824 D-44143 Dortmund Telefax: +49 231 5349423
--------------------------------------------------------------------- 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]
