hi all, I've begun using the NHibernate.Caches.Velocity implementation today. I'm updating the code to be compatible with the newer version (aka AppFabric Caching Services). To do so, I used the VelocityClient code from this stackoverflow question as a basis: http://stackoverflow.com/questions/3233792
I seem to be having some trouble with errors coming out of the locking implementation and I just wanted to clarify the behaviour of nhibernate caching as it relates to locking. What i'm seeing is that NHibernate is calling Lock() several times for the same key before it calls Unlock(). With the implementation of the code from the link above, this causes exceptions because its trying to add a different lock handle with same key to a dictionary (i.e. because it is already locked) None of the the NHContrib caches apart from this one seem to implement locking yet so i'm curious as to whether its a bug with NHibernate or if its intended behaviour and it is expected that locking implementations ignore the case where the item is already locked. Is anybody able to provide any clarity around this locking functionality? thanks, Fatal -- You received this message because you are subscribed to the Google Groups "NHibernate Contrib - Development Group" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhcdevs?hl=en.
