jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-1793) Namespace handling in AbstractSession should be synchronized
Date Wed, 15 Oct 2008 13:11:44 GMT

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

Jukka Zitting resolved JCR-1793.

       Resolution: Fixed
    Fix Version/s: 1.5.0
         Assignee: Jukka Zitting

Resolved in revisions 704002 and 704005. Merged to the 1.5 branch.

> 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
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 1.5.0
> 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.

View raw message