Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of jukka.zitting@gmail.com
 designates 64.233.184.234 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type
         :content-transfer-encoding:content-disposition;
        b=sX+/gr16S9//jCYROz/kD7D7iV+CWSauhxYThnPFuFORkqLz+abkSEVkoeQQGK+F7X
         qXxNB1v3GnmVfFy9PJW+ahIxP6ZJE9jDICO8knwg2ep6DePhtQ7WeWQ+QGA7mnQp7/fw
         0j2tSX7NHHZCdueXo/Jmphf5PIG9HbNuCEoPY=
Message-ID: <510143ac0806250344j7923ca7ama0e483b309d96710@mail.gmail.com>
Date: Wed, 25 Jun 2008 13:44:45 +0300
From: "Jukka Zitting" <jukka.zitting@gmail.com>
To: dev@jackrabbit.apache.org
Subject: The concurrent library (Re: Locking issues with XAItemStateManager -
 help appreciated)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

[Moving the thread to dev@]

On Wed, Jun 25, 2008 at 1:31 PM, sbarriba <sbarriba@yahoo.co.uk> wrote:
> ...and as an aside I note from
> http://g.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html
> That concurrent 1.3.4 is now in maintenance mode.
> Is there a plan to move to java.util.concurrent within the JDK?

Jackrabbit is currently (mostly) based on Java 1.4, that doesn't yet
have the java.util.concurrent library.

There's the backport-util-concurrent library [1] that we could
(should?) migrate to before upgrading to Java 5.

However, last time I checked the required Jackrabbit modifications are
not trivial (some of the classes and semantics in concurrent 1.3.4 are
different from java.util.concurrent) so unless someone wants to
scratch that itch and provide a good patch for this I'm inclined to
stick with the what we have now.

[1] http://backport-jsr166.sourceforge.net/

BR,

Jukka Zitting