-
Bug
-
Resolution: Fixed
-
Major
-
4.3.5
-
None
There are 2 ways how repo can deal with the sessions.
- copy-on-read (eg. ModeShape) copies persisted state to transient and further changes will not be visible until refresh.
- copy-on-write (eg. JackRabbit) copies data from persistent state only when they are to be changed and all other changes are visible without the refresh.
more on http://www.day.com/specs/jcr/1.0/7.1.3.4_Seeing_Changes_Made_by_Other_Sessions.html
One possible way to deal with the issue is to force refresh using observer in the repository strategy.
Acceptance criteria
- is causing
-
MAGNOLIA-3503 Session refresh should not assume sessions are thread safe
- Closed