You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2008/12/04 16:38:44 UTC

[jira] Created: (SLING-759) Don't synchronize on jcr sessions

Don't synchronize on jcr sessions
---------------------------------

                 Key: SLING-759
                 URL: https://issues.apache.org/jira/browse/SLING-759
             Project: Sling
          Issue Type: Bug
          Components: Event
    Affects Versions: Extensions Event 2.0.2
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: Engine 2.0.4


As some jcr implementations synchronize themselves on the jcr session it's better to not base own sync code on a session.
(However as the session is wrapped in Sling this shouldn't be a problem, but as soon as it is not wrapped anymore, it becomes one,
so it's better to avoid this potential problem upfront)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (SLING-759) Don't synchronize on jcr sessions

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-759.
----------------------------------

    Resolution: Fixed

Fixed in revision723362

> Don't synchronize on jcr sessions
> ---------------------------------
>
>                 Key: SLING-759
>                 URL: https://issues.apache.org/jira/browse/SLING-759
>             Project: Sling
>          Issue Type: Bug
>          Components: Event
>    Affects Versions: Extensions Event 2.0.2
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Engine 2.0.4
>
>
> As some jcr implementations synchronize themselves on the jcr session it's better to not base own sync code on a session.
> (However as the session is wrapped in Sling this shouldn't be a problem, but as soon as it is not wrapped anymore, it becomes one,
> so it's better to avoid this potential problem upfront)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.