Hi Anjan I'd also suggest you to update to a more recent version of castor as lot of things have changed since 0.9.5.3.
As far as I know there is no open issue about problems with caching at the moment and I can not remember that someone else reported similar issues. Anyway it may be possible that you found a new bug as I don't have an idea yet what could cause your problem. It may be best if you open a new issue in jira (our bugtracking system) but you realy should provide us with a test case attached to the new issue. According to my experice it will be imposible to reproduce your problem and prepare a fix for it if we don't have a testcase from you available. Regards Ralf Werner Guttmann schrieb: > Hi Anjan, > > as fas as I remember, the feature(s) described by Ralf are available for > more recent releases only, i.e. 0.9.9 and later. Especially the > CacheManager class has only been added 'recently'. > > Regards > Werner Guttmann > > ________________________________ > > From: Avalivin Jhons [mailto:[EMAIL PROTECTED] > Sent: Montag, 06. Februar 2006 10:51 > To: [email protected]; [email protected] > Subject: Re: [castor-dev] Cacheing Problem in Web Application > > > > Thanks Ralf, > The cache type is already set to "none" by <cache-type > cache="none"/> and attempt is also made in the code to clear the cache > by db.expireCache(ClassArray,ObjectArray) once the objects being > fetched from db. Seems like <cache-type cache="none"/> can't stop the > caching behaviour of castor, nor Database.expireCache(Class[], Object[]) > works. I am using Castor-0.9.5.3.jar. Is this a bug? > Thanks, > Anjan > > > > Ralf Joachim <[EMAIL PROTECTED]> wrote: > > Hi Avalivin, > > The best would be if you also add the object of step 2 > through castor. > If you do so castor would know that the object loaded in > step 3 has changed. > > Another option is the switch off caching for the class > in question by > setting . > > The third posibility is to clean up the cache by hand > through CacheManager. > > Regards > Ralf > > > Avalivin Jhons schrieb: > > Hi [EMAIL PROTECTED] , please have a look. > > My web application uses Castor jdo and I have seen the > problem explained > > below. > > Step 1: A Servlet makes an OQL and fetches an object > and the object is > > displayed. > > > > Step 2: In the next request the Servlet adds an object > to the object > > receiver in the first request through jdbc, and > commits. > > > > Step3. Servlet makes an OQL (same as Step 1) but > doesn't display the > > object added in the Step2. > > > > Instead of making a new OQL to get new object, Castor > returns the object > > retrieved in the previous request. > > > > How to stop this behaviour of castor? > > > > When the server is restarted the objects added in the > Step2 are > > displayed in the first request. > > > > Avalovin. > > > > Send instant messages to your online friends > http://uk.messenger.yahoo.com > > > > ------------------------------------------------- > If you wish to unsubscribe from this list, please > send an empty message to the following address: > > [EMAIL PROTECTED] > ------------------------------------------------- > > > > > Send instant messages to your online friends > http://uk.messenger.yahoo.com > > > ------------------------------------------------- > If you wish to unsubscribe from this list, please > send an empty message to the following address: > > [EMAIL PROTECTED] > ------------------------------------------------- -- Syscon Ingenieurbüro für Meß- und Datentechnik GmbH Ralf Joachim Raiffeisenstraße 11 D-72127 Kusterdingen Germany Tel. +49 7071 3690 52 Mobil: +49 173 9630135 Fax +49 7071 3690 98 Email: [EMAIL PROTECTED] Web: www.syscon-world.de ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] -------------------------------------------------
