Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 76482 invoked from network); 8 Oct 2008 13:15:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Oct 2008 13:15:16 -0000 Received: (qmail 78274 invoked by uid 500); 8 Oct 2008 13:15:06 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 78244 invoked by uid 500); 8 Oct 2008 13:15:06 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 78228 invoked by uid 99); 8 Oct 2008 13:15:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Oct 2008 06:15:06 -0700 X-ASF-Spam-Status: No, hits=-1999.9 required=10.0 tests=ALL_TRUSTED,DNS_FROM_SECURITYSAGE X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Oct 2008 13:14:10 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id B22D6234C210 for ; Wed, 8 Oct 2008 06:14:46 -0700 (PDT) Message-ID: <1586514795.1223471686728.JavaMail.jira@brutus> Date: Wed, 8 Oct 2008 06:14:46 -0700 (PDT) From: "Jukka Zitting (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Created: (JCR-1793) The abstract base classes in jcr-commons should be synchronized MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org The abstract base classes in jcr-commons 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 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.