Please tell me the correct way to reattatch an object stored in System.Web.Caching.Cache to a "new" session object. I have tried several ways to do this and experienced problems for example when saving objects that is reattatched to session after getting it from System.Web.Caching.Cache.

It's a webapplication and i'm opening a new session for each request and closing it on request end.

I'm trying to build my own cache that is not implementing the NHibernate.Cache.ICache

I have tried to use NHibernate.Caches.SysCache but seems to delete all objects/lists of type(T) when saving one object of type(T), but maybe i'm wrong. If this is the case I'm not so happy about it ;-)

I'm using NHibernate-1.2.0.Beta3

/A

This is a bad idea in general, what you end up doing is re associating the object with more than a single session at a time - because you are using the same instance in multiply requests. This is obviously not thread safe.

NHibernate doesn't evict all objects of T from the cache for a single update, maybe you are thinking about the query cache?

Yes, I was thinking about the querycache.

So, is this a good practice:

Get objects from cache when used for read-only purpose, ie. you as a developer has to decide to get objects in read-only mode or not. Read-only objects is stored in cache and loaded from cache and can not be updated in db.

In applicationcode that updates objects you have to load them from db (Session.Load) and perform the update and then remove assosiated objects in cache.

/A

But you can always do a clone of the object stored in cache.