Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 43826 invoked from network); 29 Aug 2007 12:03:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Aug 2007 12:03:59 -0000 Received: (qmail 93354 invoked by uid 500); 29 Aug 2007 12:03:53 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 93329 invoked by uid 500); 29 Aug 2007 12:03:53 -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 93320 invoked by uid 99); 29 Aug 2007 12:03:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Aug 2007 05:03:53 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Aug 2007 12:04:53 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 03C9D7141F2 for ; Wed, 29 Aug 2007 05:03:35 -0700 (PDT) Message-ID: <6671751.1188389014773.JavaMail.jira@brutus> Date: Wed, 29 Aug 2007 05:03:34 -0700 (PDT) From: "Jukka Zitting (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Commented: (JCR-953) Support for transactions when using JCR over RMI. In-Reply-To: <8713910.1180526656700.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/JCR-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523551 ] Jukka Zitting commented on JCR-953: ----------------------------------- Looks nice, thanks a lot! The only concern I have is about the additional jackrabbit-core dependency. Perhaps we should move org.apache.jackrabbit.core.XASession to jackrabbit-api. I'll file a separate issue for that. > Support for transactions when using JCR over RMI. > ------------------------------------------------- > > Key: JCR-953 > URL: https://issues.apache.org/jira/browse/JCR-953 > Project: Jackrabbit > Issue Type: Improvement > Components: rmi > Reporter: Berry van Halderen > Priority: Minor > Attachments: patch, test.zip > > > At this time, the sessions obtained from o.a.j.rmi.client.LocalAdapterFactory do not implement the methods for the XASession. Therefor the RMI access layer does not support a transactional session. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.