Re: [castor-dev] Cacheing Problem in Web Application

[Avalivin Jhons]

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