[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Haderka resolved MAGNOLIA-3261.
-----------------------------------

    Fix Version/s: 4.4.x
       Resolution: Fixed

> Concurrent session changes are not visible when repository uses copy-on-read 
> strategy
> -------------------------------------------------------------------------------------
>
>                 Key: MAGNOLIA-3261
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3261
>             Project: Magnolia
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 4.3.5
>            Reporter: Jan Haderka
>            Assignee: Jan Haderka
>             Fix For: 4.4.x
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to