Are you sure that you want to do this using iBATIS? I think you should use the 
iBATIS cache if you want to be
able to purge the cache depending on certain inserts. In you case I would do 
the caching  one layer above,
e.g. withing the (possible spring) service layer using some caching framework 
like JBoss Cache, EHCACHE, or
one of the other caching solutions.

Regards

Kai

--- Original Nachricht ---
Absender: Chema
Datum: 12.11.2008 08:58
> Ok, thanks.
> But I don't need a different object per session because are read-only objects.
> And I don't know if serialization could affect to performance.
> 
> By now,  I'll use a static hashmap
> 
> 
> 
> 2008/11/11 Larry Meadors <[EMAIL PROTECTED]>:
>> If you make your cache serializable it can be shared across sessions.
>>
>> On Tue, Nov 11, 2008 at 1:29 AM, Chema <[EMAIL PROTECTED]> wrote:
>>> I'd like to know who can to read all these cached objects.
>>> Reading docs,  looks like "read only caches" only can seen by one session.
>>> If I understood what is a session on iBatis, just one thread could see
>>> cached objects at a time.
>>
> 

Reply via email to