[jira] Updated: (JCR-1793) Namespace handling in AbstractSession should be synchronized

["Jukka Zitting (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCR-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-1793:
-------------------------------

    Description: The AbstractSession base class in o.a.j.commons implicitly assume that the session is never accessed concurrently from more than one thread and thus doesn't synchronize access to the namespace map. This causes problems when the session *is* accessed concurrently. Instead of relying on client code we should enforce thread-safety by explicitly synchronizing potentially unsafe operations on the session instance.  (was: The abstract base classes like AbstractSession in o.a.j.commons implicitly assume that a session and related objects (items, etc.) associated with that session are never accessed concurrently from more than one thread. Instead of relying on client code we should enforce thread-safety by explicitly synchronizing potentially unsafe operations on the session instance.)
        Summary: Namespace handling in AbstractSession should be synchronized  (was: The abstract base classes in jcr-commons should be synchronized)

Limited the scope of this issue to cover only namespace handling in AbstractSession. Let's cover the larger topic of sessions vs. threads in another issue.

> Namespace handling in AbstractSession should be synchronized
> ------------------------------------------------------------
>
>                 Key: JCR-1793
>                 URL: https://issues.apache.org/jira/browse/JCR-1793
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-jcr-commons
>            Reporter: Jukka Zitting
>            Priority: Minor
>
> The AbstractSession base class in o.a.j.commons implicitly assume that the session is never accessed concurrently from more than one thread and thus doesn't synchronize access to the namespace map. This causes problems when the session *is* accessed concurrently. Instead of relying on client code we should enforce thread-safety by explicitly synchronizing potentially unsafe operations on the session instance.

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