I don't think I would be better off with making sure that all 25 or so Spring Repositories that work on the cached entities don't cache if I don't find an easy way to configure that. If for some reason someone that is not familiar with the whole caching problem (and how I want to cache stuff) works with those entities in some SpringRepository or directly on Hibernate classes _massive_ errors are just to be expected.
At least so far I haven't found any way to configure the Session(s) used in the Spring Repositories (the auto implemented ones).
It would help me big time if I could selectively _enable_ the cache for sessions instead of _disabling_ them in the places a cache would do _harm_ as these cases are more frequent in the code . Have I overlooked something there?
|
