Affects Version/s: None
Fix Version/s: None
JCR-2269 i discovered that the following javax.jcr.Workspace operations are affected by potential concurency issues:
those operations directly operate on ItemState instances returned from LocalItemStateManager (LISM).
typically a workspace operation gets an ItemState instance from the LISM, does some validations,
modifies the state and finally stores it in the ChangeLog for further processing.
the problem is that the local ItemState instance is not isolated from external changes, i.e. it might change
at any point (e.g. after validation) due to external underlying changes. only when it is stored in the
ChangeLog it is disconnected from its underlying state.