19.2.4. Strategy: nonstrict read/write
If the application only occasionally needs to update data (i.e. if it is extremely unlikely that two transactions would try to update the same item simultaneously), and strict transaction isolation is not required, a
nonstrict-read-write
cache might be appropriate. If the cache is used in a JTA environment, you must specify hibernate.transaction.manager_lookup_class
. In other environments, you should ensure that the transaction is completed when Session.close()
or Session.disconnect()
is called.