When our
application need only occasionaly to update data like extremely unlikely that two transcations would try to update the same item simultaneously adn strict transaction isolation is not required, in a nonstrict-read-write cache might be appropriated. If the cache is used in a JTA environment, then we need to specify
hibernate.transaction.manager_lookup_class. When we use the other environments, then we need to ensure that the transaction is completed when
Session.close() or
Session.disconnect() is called.