incubator-sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bdelacre...@apache.org
Subject svn commit: r1553098 [4/6] - in /sling/trunk/samples/mail-archive/server: ./ src/test/java/org/apache/sling/mailarchiveserver/impl/ src/test/java/org/apache/sling/mailarchiveserver/util/ src/test/resources/ src/test/resources/test-files/ src/test/resou...
Date Mon, 23 Dec 2013 12:00:05 GMT
Added: sling/trunk/samples/mail-archive/server/src/test/resources/test-files/mbox/jackrabbit-dev-201309.mbox
URL: http://svn.apache.org/viewvc/sling/trunk/samples/mail-archive/server/src/test/resources/test-files/mbox/jackrabbit-dev-201309.mbox?rev=1553098&view=auto
==============================================================================
--- sling/trunk/samples/mail-archive/server/src/test/resources/test-files/mbox/jackrabbit-dev-201309.mbox (added)
+++ sling/trunk/samples/mail-archive/server/src/test/resources/test-files/mbox/jackrabbit-dev-201309.mbox Mon Dec 23 12:00:04 2013
@@ -0,0 +1,27113 @@
+From dev-return-38369-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Mon Sep  2 09:31:02 2013
+Return-Path: <dev-return-38369-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id 4CC79FB24
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Mon,  2 Sep 2013 09:31:02 +0000 (UTC)
+Received: (qmail 20676 invoked by uid 500); 2 Sep 2013 09:31:01 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 20281 invoked by uid 500); 2 Sep 2013 09:30:55 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 19698 invoked by uid 99); 2 Sep 2013 09:30:54 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Sep 2013 09:30:54 +0000
+Date: Mon, 2 Sep 2013 09:30:54 +0000 (UTC)
+From: "Marcel Reutegger (JIRA)" <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12665598.1377553274398.67661.1378114254170@arcas>
+In-Reply-To: <JIRA.12665598.1377553274398@arcas>
+References: <JIRA.12665598.1377553274398@arcas>
+Subject: [jira] [Resolved] (JCR-3658) MembershipCache not consistently
+ synchronized
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 7bit
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+
+     [ https://issues.apache.org/jira/browse/JCR-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
+
+Marcel Reutegger resolved JCR-3658.
+-----------------------------------
+
+       Resolution: Fixed
+    Fix Version/s: 2.7.1
+
+Applied patch in revision http://svn.apache.org/r1519376
+                
+> MembershipCache not consistently synchronized
+> ---------------------------------------------
+>
+>                 Key: JCR-3658
+>                 URL: https://issues.apache.org/jira/browse/JCR-3658
+>             Project: Jackrabbit Content Repository
+>          Issue Type: Bug
+>          Components: jackrabbit-core, security
+>    Affects Versions: 2.7
+>            Reporter: Tobias Bocanegra
+>            Assignee: Marcel Reutegger
+>            Priority: Minor
+>             Fix For: 2.7.1
+>
+>         Attachments: current.png, JCR-3658.patch, JCR-3658.patch, JCR-3658-test.patch, patched.png
+>
+>
+> the membership cache access is mostly synchronized on 'this' but in the onEvent() handler, the internal cache object is synchronized.
+> suggest: to improve cache access by a r/w lock instead.
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrators
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38370-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Mon Sep  2 10:16:54 2013
+Return-Path: <dev-return-38370-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id 7BBD1FC27
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Mon,  2 Sep 2013 10:16:54 +0000 (UTC)
+Received: (qmail 75029 invoked by uid 500); 2 Sep 2013 10:16:54 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 74795 invoked by uid 500); 2 Sep 2013 10:16:53 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 74765 invoked by uid 99); 2 Sep 2013 10:16:52 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Sep 2013 10:16:52 +0000
+Date: Mon, 2 Sep 2013 10:16:52 +0000 (UTC)
+From: "Shashank Gupta (JIRA)" <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12664593.1376996543940.67869.1378117012542@arcas>
+In-Reply-To: <JIRA.12664593.1376996543940@arcas>
+References: <JIRA.12664593.1376996543940@arcas>
+Subject: [jira] [Commented] (JCR-3651) S3 Datastore implementation
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 7bit
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+
+    [ https://issues.apache.org/jira/browse/JCR-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756002#comment-13756002 ] 
+
+Shashank Gupta commented on JCR-3651:
+-------------------------------------
+
+Thanks [~tmueller]. I have incorporated all your comments. commit Id: https://github.com/shashank-itbhu/jackrabbit/commit/502253e2f9a0e0f56b3cc0be7e919825479c2ff1
+                
+> S3 Datastore implementation
+> ---------------------------
+>
+>                 Key: JCR-3651
+>                 URL: https://issues.apache.org/jira/browse/JCR-3651
+>             Project: Jackrabbit Content Repository
+>          Issue Type: Improvement
+>          Components: jackrabbit-core
+>    Affects Versions: 2.7
+>            Reporter: Shashank Gupta
+>             Fix For: 2.7.1
+>
+>         Attachments: JCR-3651.patch
+>
+>
+> S3 Datastore provides capability to use Amazon S3 as datastore, thus leveraging all benefits of Amazon S3 like low cost, infinite, reliable, scalable storage.
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrators
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38371-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Mon Sep  2 10:42:45 2013
+Return-Path: <dev-return-38371-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id 5D2A5FD09
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Mon,  2 Sep 2013 10:42:45 +0000 (UTC)
+Received: (qmail 97058 invoked by uid 500); 2 Sep 2013 10:42:45 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 96707 invoked by uid 500); 2 Sep 2013 10:42:44 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 96695 invoked by uid 99); 2 Sep 2013 10:42:43 -0000
+Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Sep 2013 10:42:43 +0000
+X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
+	tests=ALL_TRUSTED
+X-Spam-Check-By: apache.org
+Received: from [140.211.11.8] (HELO aegis.apache.org) (140.211.11.8)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Sep 2013 10:42:40 +0000
+Received: from aegis.apache.org (localhost [127.0.0.1])
+	by aegis.apache.org (Postfix) with ESMTP id A6B63C109A;
+	Mon,  2 Sep 2013 10:42:19 +0000 (UTC)
+Date: Mon, 2 Sep 2013 10:42:16 +0000 (UTC)
+From: Apache Jenkins Server <jenkins@builds.apache.org>
+To: dev@jackrabbit.apache.org, mreutegg@apache.org
+Message-ID: <805689699.2914.1378118539605.JavaMail.hudson@aegis>
+In-Reply-To: <1128415574.1937.1377694007252.JavaMail.hudson@aegis>
+References: <1128415574.1937.1377694007252.JavaMail.hudson@aegis>
+Subject: Jackrabbit-trunk - Build # 2184 - Fixed
+MIME-Version: 1.0
+Content-Type: multipart/mixed; 
+	boundary="----=_Part_2913_1759119259.1378118537147"
+X-Jenkins-Job: Jackrabbit-trunk
+X-Jenkins-Result: SUCCESS
+X-Virus-Checked: Checked by ClamAV on apache.org
+
+------=_Part_2913_1759119259.1378118537147
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 7bit
+
+The Apache Jenkins build system has built Jackrabbit-trunk (build #2184)
+
+Status: Fixed
+
+Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2184/ to view the results.
+------=_Part_2913_1759119259.1378118537147--
+
+From dev-return-38372-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Mon Sep  2 12:02:54 2013
+Return-Path: <dev-return-38372-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id 356F6FEEA
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Mon,  2 Sep 2013 12:02:54 +0000 (UTC)
+Received: (qmail 75634 invoked by uid 500); 2 Sep 2013 12:02:53 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 75373 invoked by uid 500); 2 Sep 2013 12:02:53 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 75366 invoked by uid 99); 2 Sep 2013 12:02:51 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Sep 2013 12:02:51 +0000
+Date: Mon, 2 Sep 2013 12:02:51 +0000 (UTC)
+From: "Philipp Marx (JIRA)" <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12666568.1378123363155.68039.1378123371555@arcas>
+In-Reply-To: <JIRA.12666568.1378123363155@arcas>
+References: <JIRA.12666568.1378123363155@arcas>
+Subject: [jira] [Created] (JCR-3662) A lot of warn messages when importing
+ via Session#importXML (...doesn't represent a valid Authorizable)
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 7bit
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+Philipp Marx created JCR-3662:
+---------------------------------
+
+             Summary: A lot of warn messages when importing via Session#importXML (...doesn't represent a valid Authorizable)
+                 Key: JCR-3662
+                 URL: https://issues.apache.org/jira/browse/JCR-3662
+             Project: Jackrabbit Content Repository
+          Issue Type: Bug
+    Affects Versions: 2.4
+            Reporter: Philipp Marx
+            Priority: Minor
+
+
+We are exporting a part of our JCR tree via Session#exportSystemView and re-import this via Session#importXML. During the import we are seeing a lot of WARNINGS as the following:
+
+11:41:35,514 | WARN  |
+.core.security.user.UserImporter | 08e6b3e2-b55a-40fd-93f9-b92ccb8477d4
+| Cannot handle protected PropInfo
+org.apache.jackrabbit.core.xml.PropInfo@749951b8. Node node
+/content/ea/api/media/5/d/5d8e29d4-2531-b5a5-388b-
+e1d700000028-6826c36c-fce2-70a9-f6d2-90b100000028 doesn't represent a
+valid Authorizable.
+11:41:35,514 | WARN  |
+re.security.user.UserManagerImpl | 08e6b3e2-b55a-40fd-93f9-b92ccb8477d4
+| Unexpected user/group node type cu:Media
+
+The imports works fine though I am wondering why the JCR importer is trying
+to handle all of our nodes as Authorizables? We have a CND for cu:Media (in above case) if that matters.
+
+I can see that this was introduced by issue JCR-3120. But why should a perfectly valid import throwing all this warning messages?
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrators
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38373-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Tue Sep  3 07:16:04 2013
+Return-Path: <dev-return-38373-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id EBD1B1070E
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Tue,  3 Sep 2013 07:16:04 +0000 (UTC)
+Received: (qmail 28208 invoked by uid 500); 3 Sep 2013 07:16:02 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 27763 invoked by uid 500); 3 Sep 2013 07:15:56 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 27696 invoked by uid 99); 3 Sep 2013 07:15:51 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 07:15:51 +0000
+Date: Tue, 3 Sep 2013 07:15:51 +0000 (UTC)
+From: =?utf-8?Q?Claus_K=C3=B6ll_=28JIRA=29?= <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12665453.1377496210654.70016.1378192551650@arcas>
+In-Reply-To: <JIRA.12665453.1377496210654@arcas>
+References: <JIRA.12665453.1377496210654@arcas>
+Subject: [jira] [Commented] (JCR-3655) Better Locking inside LockManagerImpl
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: quoted-printable
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+
+    [ https://issues.apache.org/jira/browse/JCR-3655?page=3Dcom.atlassian.j=
+ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D137564=
+07#comment-13756407 ]=20
+
+Claus K=C3=B6ll commented on JCR-3655:
+---------------------------------
+
+Committed in revision 1519585 to trunk.
+               =20
+> Better Locking inside LockManagerImpl
+> -------------------------------------
+>
+>                 Key: JCR-3655
+>                 URL: https://issues.apache.org/jira/browse/JCR-3655
+>             Project: Jackrabbit Content Repository
+>          Issue Type: Bug
+>          Components: jackrabbit-core
+>    Affects Versions: 2.6.2, 2.7
+>            Reporter: Claus K=C3=B6ll
+>            Assignee: Claus K=C3=B6ll
+>         Attachments: JCR-3655.patch
+>
+>
+> Its possible to get a Deadlock during the TimeoutHandler is running.
+> As tried to fix that problem in JCR-3605 i found that the problem is hard=
+ to fix because of locking the
+> ItemStateManager during modifying the lock properties. It would be better=
+ to use a XAReentrantLock than the current synchronized block.
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrato=
+rs
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38374-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Tue Sep  3 07:17:56 2013
+Return-Path: <dev-return-38374-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id 9F64310712
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Tue,  3 Sep 2013 07:17:56 +0000 (UTC)
+Received: (qmail 29061 invoked by uid 500); 3 Sep 2013 07:17:54 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 29004 invoked by uid 500); 3 Sep 2013 07:17:52 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 28995 invoked by uid 99); 3 Sep 2013 07:17:52 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 07:17:52 +0000
+Date: Tue, 3 Sep 2013 07:17:52 +0000 (UTC)
+From: =?utf-8?Q?Claus_K=C3=B6ll_=28JIRA=29?= <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12665453.1377496210654.70018.1378192672424@arcas>
+In-Reply-To: <JIRA.12665453.1377496210654@arcas>
+References: <JIRA.12665453.1377496210654@arcas>
+Subject: [jira] [Updated] (JCR-3655) Better Locking inside LockManagerImpl
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: quoted-printable
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+
+     [ https://issues.apache.org/jira/browse/JCR-3655?page=3Dcom.atlassian.=
+jira.plugin.system.issuetabpanels:all-tabpanel ]
+
+Claus K=C3=B6ll updated JCR-3655:
+----------------------------
+
+       Resolution: Fixed
+    Fix Version/s: 2.7.1
+                   2.6.3
+           Status: Resolved  (was: Patch Available)
+   =20
+> Better Locking inside LockManagerImpl
+> -------------------------------------
+>
+>                 Key: JCR-3655
+>                 URL: https://issues.apache.org/jira/browse/JCR-3655
+>             Project: Jackrabbit Content Repository
+>          Issue Type: Bug
+>          Components: jackrabbit-core
+>    Affects Versions: 2.6.2, 2.7
+>            Reporter: Claus K=C3=B6ll
+>            Assignee: Claus K=C3=B6ll
+>             Fix For: 2.6.3, 2.7.1
+>
+>         Attachments: JCR-3655.patch
+>
+>
+> Its possible to get a Deadlock during the TimeoutHandler is running.
+> As tried to fix that problem in JCR-3605 i found that the problem is hard=
+ to fix because of locking the
+> ItemStateManager during modifying the lock properties. It would be better=
+ to use a XAReentrantLock than the current synchronized block.
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrato=
+rs
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38375-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Tue Sep  3 07:17:57 2013
+Return-Path: <dev-return-38375-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id A22E210713
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Tue,  3 Sep 2013 07:17:56 +0000 (UTC)
+Received: (qmail 29103 invoked by uid 500); 3 Sep 2013 07:17:54 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 29006 invoked by uid 500); 3 Sep 2013 07:17:53 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 28986 invoked by uid 99); 3 Sep 2013 07:17:52 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 07:17:52 +0000
+Date: Tue, 3 Sep 2013 07:17:51 +0000 (UTC)
+From: =?utf-8?Q?Claus_K=C3=B6ll_=28JIRA=29?= <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12665453.1377496210654.70017.1378192671569@arcas>
+In-Reply-To: <JIRA.12665453.1377496210654@arcas>
+References: <JIRA.12665453.1377496210654@arcas>
+Subject: [jira] [Commented] (JCR-3655) Better Locking inside LockManagerImpl
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: quoted-printable
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+
+    [ https://issues.apache.org/jira/browse/JCR-3655?page=3Dcom.atlassian.j=
+ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D137564=
+08#comment-13756408 ]=20
+
+Claus K=C3=B6ll commented on JCR-3655:
+---------------------------------
+
+Committed in revision 1519586 to 2.6.x branch ..
+               =20
+> Better Locking inside LockManagerImpl
+> -------------------------------------
+>
+>                 Key: JCR-3655
+>                 URL: https://issues.apache.org/jira/browse/JCR-3655
+>             Project: Jackrabbit Content Repository
+>          Issue Type: Bug
+>          Components: jackrabbit-core
+>    Affects Versions: 2.6.2, 2.7
+>            Reporter: Claus K=C3=B6ll
+>            Assignee: Claus K=C3=B6ll
+>         Attachments: JCR-3655.patch
+>
+>
+> Its possible to get a Deadlock during the TimeoutHandler is running.
+> As tried to fix that problem in JCR-3605 i found that the problem is hard=
+ to fix because of locking the
+> ItemStateManager during modifying the lock properties. It would be better=
+ to use a XAReentrantLock than the current synchronized block.
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrato=
+rs
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38376-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Tue Sep  3 11:29:56 2013
+Return-Path: <dev-return-38376-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id 18B0B10CCE
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Tue,  3 Sep 2013 11:29:56 +0000 (UTC)
+Received: (qmail 82027 invoked by uid 500); 3 Sep 2013 11:29:55 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 81863 invoked by uid 500); 3 Sep 2013 11:29:54 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 81781 invoked by uid 99); 3 Sep 2013 11:29:52 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 11:29:52 +0000
+Date: Tue, 3 Sep 2013 11:29:52 +0000 (UTC)
+From: "Robert Munteanu (JIRA)" <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12666680.1378207690902.70588.1378207792316@arcas>
+In-Reply-To: <JIRA.12666680.1378207690902@arcas>
+References: <JIRA.12666680.1378207690902@arcas>
+Subject: [jira] [Created] (JCR-3663) FileVault: tweak gitignore file
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 7bit
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+Robert Munteanu created JCR-3663:
+------------------------------------
+
+             Summary: FileVault: tweak gitignore file
+                 Key: JCR-3663
+                 URL: https://issues.apache.org/jira/browse/JCR-3663
+             Project: Jackrabbit Content Repository
+          Issue Type: Task
+          Components: jackrabbit-jcr-commons
+            Reporter: Robert Munteanu
+            Priority: Trivial
+
+
+After a full build the bin directory and derby.log files are shown as untracked. I'll attach a trivial patch which fixes this.
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrators
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38377-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Tue Sep  3 11:31:54 2013
+Return-Path: <dev-return-38377-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id 6EEDA10CD5
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Tue,  3 Sep 2013 11:31:54 +0000 (UTC)
+Received: (qmail 82923 invoked by uid 500); 3 Sep 2013 11:31:53 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 82859 invoked by uid 500); 3 Sep 2013 11:31:53 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 82852 invoked by uid 99); 3 Sep 2013 11:31:53 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 11:31:53 +0000
+Date: Tue, 3 Sep 2013 11:31:51 +0000 (UTC)
+From: "Robert Munteanu (JIRA)" <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12666680.1378207690902.70589.1378207911651@arcas>
+In-Reply-To: <JIRA.12666680.1378207690902@arcas>
+References: <JIRA.12666680.1378207690902@arcas>
+Subject: [jira] [Updated] (JCR-3663) FileVault: tweak gitignore file
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 7bit
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+
+     [ https://issues.apache.org/jira/browse/JCR-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
+
+Robert Munteanu updated JCR-3663:
+---------------------------------
+
+    Attachment: JCR-3663-1.patch
+    
+> FileVault: tweak gitignore file
+> -------------------------------
+>
+>                 Key: JCR-3663
+>                 URL: https://issues.apache.org/jira/browse/JCR-3663
+>             Project: Jackrabbit Content Repository
+>          Issue Type: Task
+>          Components: jackrabbit-jcr-commons
+>            Reporter: Robert Munteanu
+>            Priority: Trivial
+>         Attachments: JCR-3663-1.patch
+>
+>
+> After a full build the bin directory and derby.log files are shown as untracked. I'll attach a trivial patch which fixes this.
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrators
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38378-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Tue Sep  3 15:22:00 2013
+Return-Path: <dev-return-38378-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id 75550103E3
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Tue,  3 Sep 2013 15:22:00 +0000 (UTC)
+Received: (qmail 93794 invoked by uid 500); 3 Sep 2013 15:22:00 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 93427 invoked by uid 500); 3 Sep 2013 15:21:54 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 93413 invoked by uid 99); 3 Sep 2013 15:21:52 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 15:21:52 +0000
+Date: Tue, 3 Sep 2013 15:21:51 +0000 (UTC)
+From: "angela (JIRA)" <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12662306.1375860879961.71660.1378221711558@arcas>
+In-Reply-To: <JIRA.12662306.1375860879961@arcas>
+References: <JIRA.12662306.1375860879961@arcas>
+Subject: [jira] [Resolved] (JCR-3637) JackrabbitAccessControlEntry: Add
+ support for multi-valued restrictions
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 7bit
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+
+     [ https://issues.apache.org/jira/browse/JCR-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
+
+angela resolved JCR-3637.
+-------------------------
+
+    Resolution: Fixed
+    
+> JackrabbitAccessControlEntry: Add support for multi-valued restrictions
+> -----------------------------------------------------------------------
+>
+>                 Key: JCR-3637
+>                 URL: https://issues.apache.org/jira/browse/JCR-3637
+>             Project: Jackrabbit Content Repository
+>          Issue Type: New Feature
+>          Components: jackrabbit-api
+>            Reporter: angela
+>            Assignee: angela
+>         Attachments: JCR-3637-oak.patch, JCR-3637.patch
+>
+>
+> Currently JackrabbitAccessControlEntry can only deal with single-valued restrictions. However, it would desirable to also allow for restrictions that contain multiple values.
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrators
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38379-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Tue Sep  3 18:24:01 2013
+Return-Path: <dev-return-38379-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id 850C410A75
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Tue,  3 Sep 2013 18:24:01 +0000 (UTC)
+Received: (qmail 39403 invoked by uid 500); 3 Sep 2013 18:24:01 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 38493 invoked by uid 500); 3 Sep 2013 18:23:58 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 37821 invoked by uid 99); 3 Sep 2013 18:23:54 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 18:23:54 +0000
+Date: Tue, 3 Sep 2013 18:23:54 +0000 (UTC)
+From: "Tobias Bocanegra (JIRA)" <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12666680.1378207690902.72583.1378232634312@arcas>
+In-Reply-To: <JIRA.12666680.1378207690902@arcas>
+References: <JIRA.12666680.1378207690902@arcas>
+Subject: [jira] [Assigned] (JCR-3663) FileVault: tweak gitignore file
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 7bit
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+
+     [ https://issues.apache.org/jira/browse/JCR-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
+
+Tobias Bocanegra reassigned JCR-3663:
+-------------------------------------
+
+    Assignee: Tobias Bocanegra
+    
+> FileVault: tweak gitignore file
+> -------------------------------
+>
+>                 Key: JCR-3663
+>                 URL: https://issues.apache.org/jira/browse/JCR-3663
+>             Project: Jackrabbit Content Repository
+>          Issue Type: Task
+>          Components: jackrabbit-jcr-commons
+>            Reporter: Robert Munteanu
+>            Assignee: Tobias Bocanegra
+>            Priority: Trivial
+>         Attachments: JCR-3663-1.patch
+>
+>
+> After a full build the bin directory and derby.log files are shown as untracked. I'll attach a trivial patch which fixes this.
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrators
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38380-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Tue Sep  3 18:26:01 2013
+Return-Path: <dev-return-38380-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id 22D8E10A88
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Tue,  3 Sep 2013 18:26:01 +0000 (UTC)
+Received: (qmail 43121 invoked by uid 500); 3 Sep 2013 18:25:55 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 42888 invoked by uid 500); 3 Sep 2013 18:25:55 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 42651 invoked by uid 99); 3 Sep 2013 18:25:53 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 18:25:53 +0000
+Date: Tue, 3 Sep 2013 18:25:53 +0000 (UTC)
+From: "Tobias Bocanegra (JIRA)" <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12666680.1378207690902.72594.1378232753506@arcas>
+In-Reply-To: <JIRA.12666680.1378207690902@arcas>
+References: <JIRA.12666680.1378207690902@arcas>
+Subject: [jira] [Resolved] (JCR-3663) FileVault: tweak gitignore file
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 7bit
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+
+     [ https://issues.apache.org/jira/browse/JCR-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
+
+Tobias Bocanegra resolved JCR-3663.
+-----------------------------------
+
+    Resolution: Fixed
+
+patch applied in revision 1519783.
+                
+> FileVault: tweak gitignore file
+> -------------------------------
+>
+>                 Key: JCR-3663
+>                 URL: https://issues.apache.org/jira/browse/JCR-3663
+>             Project: Jackrabbit Content Repository
+>          Issue Type: Task
+>          Components: jackrabbit-jcr-commons
+>            Reporter: Robert Munteanu
+>            Assignee: Tobias Bocanegra
+>            Priority: Trivial
+>         Attachments: JCR-3663-1.patch
+>
+>
+> After a full build the bin directory and derby.log files are shown as untracked. I'll attach a trivial patch which fixes this.
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrators
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38381-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Tue Sep  3 19:20:00 2013
+Return-Path: <dev-return-38381-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id 423CD10CD6
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Tue,  3 Sep 2013 19:20:00 +0000 (UTC)
+Received: (qmail 14006 invoked by uid 500); 3 Sep 2013 19:19:59 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 11640 invoked by uid 500); 3 Sep 2013 19:19:55 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 11004 invoked by uid 99); 3 Sep 2013 19:19:53 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 19:19:53 +0000
+Date: Tue, 3 Sep 2013 19:19:53 +0000 (UTC)
+From: "Jukka Zitting (JIRA)" <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12666680.1378207690902.72991.1378235993923@arcas>
+In-Reply-To: <JIRA.12666680.1378207690902@arcas>
+References: <JIRA.12666680.1378207690902@arcas>
+Subject: [jira] [Commented] (JCR-3663) FileVault: tweak gitignore file
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 7bit
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+
+    [ https://issues.apache.org/jira/browse/JCR-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756950#comment-13756950 ] 
+
+Jukka Zitting commented on JCR-3663:
+------------------------------------
+
+A better solution would be to tweak the build so that everything it produces goes inside the target folder. See the jackrabbit-core POM for an example on how to do that for the derby.log file (search for derby.stream.error.file).
+                
+> FileVault: tweak gitignore file
+> -------------------------------
+>
+>                 Key: JCR-3663
+>                 URL: https://issues.apache.org/jira/browse/JCR-3663
+>             Project: Jackrabbit Content Repository
+>          Issue Type: Task
+>          Components: jackrabbit-jcr-commons
+>            Reporter: Robert Munteanu
+>            Assignee: Tobias Bocanegra
+>            Priority: Trivial
+>         Attachments: JCR-3663-1.patch
+>
+>
+> After a full build the bin directory and derby.log files are shown as untracked. I'll attach a trivial patch which fixes this.
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrators
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38382-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Tue Sep  3 23:45:03 2013
+Return-Path: <dev-return-38382-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id D248A106C7
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Tue,  3 Sep 2013 23:45:03 +0000 (UTC)
+Received: (qmail 89293 invoked by uid 500); 3 Sep 2013 23:45:03 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 89222 invoked by uid 500); 3 Sep 2013 23:45:03 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 89215 invoked by uid 99); 3 Sep 2013 23:45:02 -0000
+Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 23:45:02 +0000
+Received: from localhost (HELO mail-vc0-f171.google.com) (127.0.0.1)
+  (smtp-auth username tripod, mechanism plain)
+  by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 23:45:02 +0000
+Received: by mail-vc0-f171.google.com with SMTP id ij15so4386551vcb.2
+        for <dev@jackrabbit.apache.org>; Tue, 03 Sep 2013 16:45:01 -0700 (PDT)
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
+        d=1e100.net; s=20130820;
+        h=x-gm-message-state:mime-version:date:message-id:subject:from:to
+         :content-type;
+        bh=fmHEqmVHyNiTh8VZvrCnjKyemOjpkDW0tlGfo1ewygk=;
+        b=Y2JA3xcyGhaMaXxEe61CaJlwOVEyYn6DgVmQkrp7dY1aOlhy/frBizxRX8CzXqIwRk
+         DbUKjfgZicrP2Y6hF++ca4exhi6ANds4AyWjUJGBp/iF1PcOISPtLgra8eyiPL4wjvZH
+         29C9tVefYYi/SXN37PRg16bh7MbCtZ2f1QsjzXfUY7LqkVlScqq4z9kBJE4zeRrMi9Ya
+         6+kV5v0wazOdG2hOcSkNS1WFD2VaoTKS/u866F4DNBOxfUocjndctzWXSAgvYPA9f9GM
+         BJp38rlUkmp0qglXK+P6FpoZpEcAzuwuVfM+Q0gtQLEFlAIg+2e1DTAuxJ9TNv1SHU/d
+         GVqg==
+X-Gm-Message-State: ALoCoQnJGOpySWXiNk1TNRCH5sCUROnhH3Z4RMLhtVTY1hqqFyRZzfWKXU0nPXgfSX7Y+lhX845V
+MIME-Version: 1.0
+X-Received: by 10.220.65.134 with SMTP id j6mr32136vci.78.1378251901515; Tue,
+ 03 Sep 2013 16:45:01 -0700 (PDT)
+Received: by 10.52.171.83 with HTTP; Tue, 3 Sep 2013 16:45:01 -0700 (PDT)
+Date: Tue, 3 Sep 2013 16:45:01 -0700
+Message-ID: <CAB+dfin8Wx8UtpdNoc4YEVef-Rwc+YLybCV9Wm7GUuZ=Lyknxg@mail.gmail.com>
+Subject: [SITE] How is jackrabbit's website generated?
+From: Tobias Bocanegra <tripod@apache.org>
+To: "dev@jackrabbit.apache.org" <dev@jackrabbit.apache.org>
+Content-Type: text/plain; charset=UTF-8
+
+Hi,
+
+looking at the explanations here [0] it states that the website is
+generated with svnpubsub using the content at [1]. In the repository
+[1] I see *.cwiki and *.mdtext. From reading the Apache CMS docu at
+[2] it looks like only the mdtext files are needed.
+
+So what's the best way to write documentation? using the svn checkout
+and offline editors like Mou or directly via the Apache CMS ?
+
+Regards, Toby
+
+
+[0] http://wiki.apache.org/jackrabbit/JackrabbitWebsite
+[1] https://svn.apache.org/repos/asf/jackrabbit/site/live/
+[2] http://www.apache.org/dev/cmsref#markdown
+
+From dev-return-38383-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Wed Sep  4 09:55:12 2013
+Return-Path: <dev-return-38383-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id DFF8510629
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Wed,  4 Sep 2013 09:55:11 +0000 (UTC)
+Received: (qmail 67352 invoked by uid 500); 4 Sep 2013 09:55:11 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 66940 invoked by uid 500); 4 Sep 2013 09:55:01 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 66580 invoked by uid 99); 4 Sep 2013 09:54:57 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Sep 2013 09:54:57 +0000
+Date: Wed, 4 Sep 2013 09:54:57 +0000 (UTC)
+From: "Shashank Gupta (JIRA)" <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12664593.1376996543940.76773.1378288497624@arcas>
+In-Reply-To: <JIRA.12664593.1376996543940@arcas>
+References: <JIRA.12664593.1376996543940@arcas>
+Subject: [jira] [Updated] (JCR-3651) S3 Datastore implementation
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 7bit
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+
+     [ https://issues.apache.org/jira/browse/JCR-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
+
+Shashank Gupta updated JCR-3651:
+--------------------------------
+
+    Attachment: JCR-3651-svn.patch
+
+Attached svn compatible patch. 
+                
+> S3 Datastore implementation
+> ---------------------------
+>
+>                 Key: JCR-3651
+>                 URL: https://issues.apache.org/jira/browse/JCR-3651
+>             Project: Jackrabbit Content Repository
+>          Issue Type: Improvement
+>          Components: jackrabbit-core
+>    Affects Versions: 2.7
+>            Reporter: Shashank Gupta
+>             Fix For: 2.7.1
+>
+>         Attachments: JCR-3651.patch, JCR-3651-svn.patch
+>
+>
+> S3 Datastore provides capability to use Amazon S3 as datastore, thus leveraging all benefits of Amazon S3 like low cost, infinite, reliable, scalable storage.
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrators
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38384-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Wed Sep  4 10:19:54 2013
+Return-Path: <dev-return-38384-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id 24846106C3
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Wed,  4 Sep 2013 10:19:54 +0000 (UTC)
+Received: (qmail 3822 invoked by uid 500); 4 Sep 2013 10:19:53 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 3354 invoked by uid 500); 4 Sep 2013 10:19:52 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 3261 invoked by uid 99); 4 Sep 2013 10:19:51 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Sep 2013 10:19:51 +0000
+Date: Wed, 4 Sep 2013 10:19:51 +0000 (UTC)
+From: "Thomas Mueller (JIRA)" <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12664593.1376996543940.76869.1378289991824@arcas>
+In-Reply-To: <JIRA.12664593.1376996543940@arcas>
+References: <JIRA.12664593.1376996543940@arcas>
+Subject: [jira] [Commented] (JCR-3651) S3 Datastore implementation
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 7bit
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+
+    [ https://issues.apache.org/jira/browse/JCR-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757627#comment-13757627 ] 
+
+Thomas Mueller commented on JCR-3651:
+-------------------------------------
+
+Hi,
+
+Some more comments. There are many "Java beginners" errors in the code.
+
+Don't initialize fields to their default value (null, false,...) :
+
+{code}
+protected String config = null;
+{code}
+
+Instead, simply use:
+
+{code}
+protected String config;
+{code}
+
+In the test class hierarchy there are duplicate fields, similar to:
+
+{code}
+class TestBase {
+    protected String config;
+}
+class TestExtends extends TestBase {
+    protected String config;
+}
+{code}
+
+The second field hides the field in TestBase.
+
+Many of the Javadocs comments are low quality; they don't add any valuable information. They should either be removed or a meaningful description should be added. Example:
+
+{code}
++     * @param store
++     * @param homeDir
++     * @param config
++     * @throws DataStoreException
++     */
++    void init(CachingDataStore store, String homeDir, String config) throws DataStoreException;
+{code}
+
+Also, javadocs of the following type are basically no-ops and should be removed:
+
+{code}
++    /**
++     * @inheritDoc
++     */
+{code}
+
+There are some comments "// TODO Auto-generated method stub", they should be removed.
+
+I suggest to use an IDE such as Eclipse or IntelliJ, enable code warnings and go though that list and fix the warnings. Also, I suggest to use Checkstyle.
+
+
+
+                
+> S3 Datastore implementation
+> ---------------------------
+>
+>                 Key: JCR-3651
+>                 URL: https://issues.apache.org/jira/browse/JCR-3651
+>             Project: Jackrabbit Content Repository
+>          Issue Type: Improvement
+>          Components: jackrabbit-core
+>    Affects Versions: 2.7
+>            Reporter: Shashank Gupta
+>             Fix For: 2.7.1
+>
+>         Attachments: JCR-3651.patch, JCR-3651-svn.patch
+>
+>
+> S3 Datastore provides capability to use Amazon S3 as datastore, thus leveraging all benefits of Amazon S3 like low cost, infinite, reliable, scalable storage.
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrators
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38385-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Wed Sep  4 14:06:04 2013
+Return-Path: <dev-return-38385-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id 0E08C10C82
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Wed,  4 Sep 2013 14:06:04 +0000 (UTC)
+Received: (qmail 10311 invoked by uid 500); 4 Sep 2013 14:06:04 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 9872 invoked by uid 500); 4 Sep 2013 14:05:57 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 9660 invoked by uid 99); 4 Sep 2013 14:05:54 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Sep 2013 14:05:54 +0000
+Date: Wed, 4 Sep 2013 14:05:54 +0000 (UTC)
+From: "Chris Poulsen (JIRA)" <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12665663.1377589415673.77750.1378303554652@arcas>
+In-Reply-To: <JIRA.12665663.1377589415673@arcas>
+References: <JIRA.12665663.1377589415673@arcas>
+Subject: [jira] [Commented] (JCR-3659) VersionManager.getVersionHistory
+ followed by VersionManager.checkpoint in transaction fails
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 7bit
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+
+    [ https://issues.apache.org/jira/browse/JCR-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757792#comment-13757792 ] 
+
+Chris Poulsen commented on JCR-3659:
+------------------------------------
+
+I've just been bit by this again :( 
+
+It seems like performing the following two steps:
+1) VersionManager.getVersionHistory(<checked-out-path>)
+2) VersionManager.checkpoint(<checked-out-path>)
+
+Makes the last step fail with the error in the issue... But only if the session is enlisted in a transaction.
+
+Can someone explain why performing this in a (XA)transaction fails, but works like expected in a non-transactional environment? 
+There are no pending changes or anything, but it seems like jackrabbit is trying to do access some undefined version or something weird like that during check-in in the transactional case.
+                
+> VersionManager.getVersionHistory followed by VersionManager.checkpoint in transaction fails
+> -------------------------------------------------------------------------------------------
+>
+>                 Key: JCR-3659
+>                 URL: https://issues.apache.org/jira/browse/JCR-3659
+>             Project: Jackrabbit Content Repository
+>          Issue Type: Bug
+>    Affects Versions: 2.4.4, 2.6.3
+>         Environment: Atomikos TX manager, H2 database (in-memory) 
+>            Reporter: Chris Poulsen
+>         Attachments: test-jcr3659.zip
+>
+>
+> I'm seeing the exception below when performing the following operations: 
+> Tx-1 (Bootstrap node):
+> <begin transaction>
+>   1) Create mix:versionable node called "node" in repository root.
+>   2) Session.save()
+>   3) VersionManager.checkpoint( "/node" )
+> <finish transaction>
+> Then I do:
+> Tx-2 (Simplified code that fails):
+> <begin transaction>
+>   1) Get version history by doing VersionManager.getVersionHistory( "/node" ) (do nothing with the return value)
+>   2) VersionManager.checkpoint( "/node" )
+> <finish transaction>
+> java.lang.RuntimeException: javax.jcr.InvalidItemStateException: Could not find child 35932dba-2ca3-40d8-94a9-762f2328be59 of node 3d10e0a6-0e8e-4ff5-8c9b-f75ccd63816d
+>     at com.dezide.webauthor.core.dao.JackrabbitTest$2.doInTransactionWithoutResult(JackrabbitTest.java:65)
+>     at org.springframework.transaction.support.TransactionCallbackWithoutResult.doInTransaction(TransactionCallbackWithoutResult.java:33)
+>     at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:131)
+>     at com.dezide.webauthor.core.dao.JackrabbitTest.testVersionHistoryBug(JackrabbitTest.java:47)
+>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
+>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
+>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
+>     at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
+>     at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
+>     at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
+>     at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
+>     at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
+>     at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
+>     at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
+>     at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
+>     at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
+>     at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
+>     at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
+>     at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
+>     at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
+>     at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
+>     at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
+>     at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
+>     at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
+>     at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74)
+>     at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:202)
+>     at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:65)
+>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
+>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
+>     at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)
+> Caused by: javax.jcr.InvalidItemStateException: Could not find child 35932dba-2ca3-40d8-94a9-762f2328be59 of node 3d10e0a6-0e8e-4ff5-8c9b-f75ccd63816d
+>     at org.apache.jackrabbit.core.ItemManager.getDefinition(ItemManager.java:207)
+>     at org.apache.jackrabbit.core.ItemData.getDefinition(ItemData.java:99)
+>     at org.apache.jackrabbit.core.ItemManager.canRead(ItemManager.java:421)
+>     at org.apache.jackrabbit.core.ItemManager.createItemData(ItemManager.java:843)
+>     at org.apache.jackrabbit.core.ItemManager.getItemData(ItemManager.java:391)
+>     at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:328)
+>     at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:622)
+>     at org.apache.jackrabbit.core.SessionImpl.getNodeById(SessionImpl.java:536)
+>     at org.apache.jackrabbit.core.VersionManagerImpl$3.perform(VersionManagerImpl.java:162)
+>     at org.apache.jackrabbit.core.VersionManagerImpl$3.perform(VersionManagerImpl.java:154)
+>     at org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
+>     at org.apache.jackrabbit.core.VersionManagerImpl.perform(VersionManagerImpl.java:96)
+>     at org.apache.jackrabbit.core.VersionManagerImpl.checkpoint(VersionManagerImpl.java:154)
+>     at com.dezide.webauthor.core.dao.JackrabbitTest$2.doInTransactionWithoutResult(JackrabbitTest.java:61)
+>     ... 32 more
+> The child node id from the exception does (obviously) not exist, while the node "3d10e0a6-0e8e-4ff5-8c9b-f75ccd63816d" is of VersionHistory type (retrieved in debugger). 
+> I don't think that retrieving a version history should produce changes related to creating a checkpoint, but it seems like something happens. Moving the getVersionHistory call outside the transaction or suspending the transaction while retrieving the history get things going again, but it is not really a long term solution.
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrators
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38386-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Wed Sep  4 16:11:23 2013
+Return-Path: <dev-return-38386-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id F40BC1010B
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Wed,  4 Sep 2013 16:11:22 +0000 (UTC)
+Received: (qmail 35861 invoked by uid 500); 4 Sep 2013 16:11:22 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 35484 invoked by uid 500); 4 Sep 2013 16:11:22 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 35477 invoked by uid 99); 4 Sep 2013 16:11:21 -0000
+Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Sep 2013 16:11:21 +0000
+X-ASF-Spam-Status: No, hits=2.0 required=5.0
+	tests=SPF_NEUTRAL,URI_HEX
+X-Spam-Check-By: apache.org
+Received-SPF: error (athena.apache.org: encountered temporary error during SPF processing of domain of andreas@breakpoint.no)
+Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Sep 2013 16:11:16 +0000
+Received: from [192.168.236.139] (helo=joe.nabble.com)
+	by joe.nabble.com with esmtp (Exim 4.72)
+	(envelope-from <andreas@breakpoint.no>)
+	id 1VHFej-0000Um-4J
+	for dev@jackrabbit.apache.org; Wed, 04 Sep 2013 09:10:10 -0700
+Date: Wed, 4 Sep 2013 09:09:54 -0700 (PDT)
+From: andreas <andreas@breakpoint.no>
+To: dev@jackrabbit.apache.org
+Message-ID: <1378310993989-4659460.post@n4.nabble.com>
+Subject: Jackrabbit JCA and JTA
+MIME-Version: 1.0
+Content-Type: text/plain; charset=us-ascii
+Content-Transfer-Encoding: 7bit
+X-Virus-Checked: Checked by ClamAV on apache.org
+
+Hi
+
+I am developing an application that uses both Jackrabbit and a database. In
+Jackrabbit I store the files that I upload, and the database I store all the
+other data in the app. I am using Spring 3.2, Hibernate 4.x and Jackrabbit
+2.6.2. I have downloaded the Jackrabbit JCA version and deployed it to JBoss
+7.1.1. I have configured it correctly I think. I can upload file to it and
+it is saved. I also debugged my application and I saw that the session
+object that invoke save() and logout() on is of type XaSession. I am using
+the datastore.
+
+The way I tested my code is like this: I have one method in the service
+layer of my app annotated with @Transactional. Inside the method I first add
+a file to the content repository, then I force a RunTimeException to be
+thrown (and the code that should run instead of the exception would be to
+save my object to the database through Hibernate). I cleared the datastore
+(no files inside it) but when the exception is thrown the file that I added
+isn't removed from the datastore. 
+
+So, is this correct? Does files in datastore stay in the datastore - not
+rolled back? Or should it be removed. I am using the
+<tx:jta-transaction-manager /> annotation in Spring config. 
+
+Could someone shed some light over this because I don't understand if I got
+it working, or if I need to do something else to get it working? And where
+does the metadata of the file that I add get stored? I have configured a own
+database for the persistence manager but I don't see anything useful in the
+database tables? There are only a lot of what seems to be binary things
+there? Is there a way to verify if a file is inserted or not in the database
+even though the actual file is stored on disk (datastore)?
+
+Thank you
+
+- Andreas
+
+
+
+--
+View this message in context: http://jackrabbit.510166.n4.nabble.com/Jackrabbit-JCA-and-JTA-tp4659460.html
+Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
+
+From dev-return-38387-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Thu Sep  5 07:48:23 2013
+Return-Path: <dev-return-38387-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id BC99910FE8
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Thu,  5 Sep 2013 07:48:23 +0000 (UTC)
+Received: (qmail 35803 invoked by uid 500); 5 Sep 2013 07:48:22 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 35753 invoked by uid 500); 5 Sep 2013 07:48:14 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 35741 invoked by uid 99); 5 Sep 2013 07:48:10 -0000
+Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Sep 2013 07:48:10 +0000
+X-ASF-Spam-Status: No, hits=1.3 required=5.0
+	tests=SPF_PASS,URI_HEX
+X-Spam-Check-By: apache.org
+Received-SPF: pass (athena.apache.org: local policy)
+Received: from [195.137.237.88] (HELO vps.dezide.dk) (195.137.237.88)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Sep 2013 07:48:05 +0000
+Received: from [10.0.0.92] (unknown [87.116.17.14])
+	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
+	(No client certificate requested)
+	by vps.dezide.dk (Postfix) with ESMTP id 6F39B184016
+	for <dev@jackrabbit.apache.org>; Thu,  5 Sep 2013 09:32:53 +0200 (CEST)
+Message-ID: <5228371D.5070705@dezide.com>
+Date: Thu, 05 Sep 2013 09:47:41 +0200
+From: Chris Poulsen <chris.poulsen@dezide.com>
+User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
+MIME-Version: 1.0
+To: dev@jackrabbit.apache.org
+Subject: Re: Jackrabbit JCA and JTA
+References: <1378310993989-4659460.post@n4.nabble.com>
+In-Reply-To: <1378310993989-4659460.post@n4.nabble.com>
+Content-Type: text/plain; charset=ISO-8859-1; format=flowed
+Content-Transfer-Encoding: 7bit
+X-Virus-Checked: Checked by ClamAV on apache.org
+
+Hi,
+
+I don't know about file storing vs. transactions, but I would expect it 
+to work like any other transactional change to the repository.
+
+Getting the JTA setup correctly can be somewhat of a tricky task - Are 
+you sure that you are in a transaction in your method (and that you are 
+in the correct transaction)?
+
+Have you tried adding a simple node in the transaction method to see if 
+a simple node is rolled back? Also you can usually ask spring and the 
+JTA provider to produce really detailed logs to help you figure out what 
+is going on.
+
+HTH.
+-- 
+Chris
+
+On 04-09-2013 18:09, andreas wrote:
+> Hi
+>
+> I am developing an application that uses both Jackrabbit and a database. In
+> Jackrabbit I store the files that I upload, and the database I store all the
+> other data in the app. I am using Spring 3.2, Hibernate 4.x and Jackrabbit
+> 2.6.2. I have downloaded the Jackrabbit JCA version and deployed it to JBoss
+> 7.1.1. I have configured it correctly I think. I can upload file to it and
+> it is saved. I also debugged my application and I saw that the session
+> object that invoke save() and logout() on is of type XaSession. I am using
+> the datastore.
+>
+> The way I tested my code is like this: I have one method in the service
+> layer of my app annotated with @Transactional. Inside the method I first add
+> a file to the content repository, then I force a RunTimeException to be
+> thrown (and the code that should run instead of the exception would be to
+> save my object to the database through Hibernate). I cleared the datastore
+> (no files inside it) but when the exception is thrown the file that I added
+> isn't removed from the datastore.
+>
+> So, is this correct? Does files in datastore stay in the datastore - not
+> rolled back? Or should it be removed. I am using the
+> <tx:jta-transaction-manager /> annotation in Spring config.
+>
+> Could someone shed some light over this because I don't understand if I got
+> it working, or if I need to do something else to get it working? And where
+> does the metadata of the file that I add get stored? I have configured a own
+> database for the persistence manager but I don't see anything useful in the
+> database tables? There are only a lot of what seems to be binary things
+> there? Is there a way to verify if a file is inserted or not in the database
+> even though the actual file is stored on disk (datastore)?
+>
+> Thank you
+>
+> - Andreas
+>
+>
+>
+> --
+> View this message in context: http://jackrabbit.510166.n4.nabble.com/Jackrabbit-JCA-and-JTA-tp4659460.html
+> Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
+
+
+From dev-return-38388-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Thu Sep  5 14:25:04 2013
+Return-Path: <dev-return-38388-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id 4225310C2F
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Thu,  5 Sep 2013 14:25:04 +0000 (UTC)
+Received: (qmail 17001 invoked by uid 500); 5 Sep 2013 14:25:03 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 16557 invoked by uid 500); 5 Sep 2013 14:24:57 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 16517 invoked by uid 99); 5 Sep 2013 14:24:53 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Sep 2013 14:24:53 +0000
+Date: Thu, 5 Sep 2013 14:24:53 +0000 (UTC)
+From: "Robert Munteanu (JIRA)" <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12667115.1378391071230.85273.1378391093443@arcas>
+In-Reply-To: <JIRA.12667115.1378391071230@arcas>
+References: <JIRA.12667115.1378391071230@arcas>
+Subject: [jira] [Created] (JCR-3664) FileVault: fix javadoc for
+ PlatformNameFormatter
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 7bit
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+Robert Munteanu created JCR-3664:
+------------------------------------
+
+             Summary: FileVault: fix javadoc for PlatformNameFormatter
+                 Key: JCR-3664
+                 URL: https://issues.apache.org/jira/browse/JCR-3664
+             Project: Jackrabbit Content Repository
+          Issue Type: Task
+          Components: jackrabbit-jcr-commons
+            Reporter: Robert Munteanu
+            Priority: Trivial
+
+
+The javadoc for this class is incorrectly formatted - it is written as plain text rather than HTML. It's missing some p and pre tags to make it render as expected.
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrators
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38390-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Thu Sep  5 14:28:56 2013
+Return-Path: <dev-return-38390-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id 19F2D10C41
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Thu,  5 Sep 2013 14:28:56 +0000 (UTC)
+Received: (qmail 20386 invoked by uid 500); 5 Sep 2013 14:28:54 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 20257 invoked by uid 500); 5 Sep 2013 14:28:53 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 20234 invoked by uid 99); 5 Sep 2013 14:28:52 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Sep 2013 14:28:52 +0000
+Date: Thu, 5 Sep 2013 14:28:52 +0000 (UTC)
+From: "Robert Munteanu (JIRA)" <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12667115.1378391071230.85281.1378391332271@arcas>
+In-Reply-To: <JIRA.12667115.1378391071230@arcas>
+References: <JIRA.12667115.1378391071230@arcas>
+Subject: [jira] [Updated] (JCR-3664) FileVault: fix javadoc for
+ PlatformNameFormatter
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 7bit
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+
+     [ https://issues.apache.org/jira/browse/JCR-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
+
+Robert Munteanu updated JCR-3664:
+---------------------------------
+
+    Status: Patch Available  (was: Open)
+    
+> FileVault: fix javadoc for PlatformNameFormatter
+> ------------------------------------------------
+>
+>                 Key: JCR-3664
+>                 URL: https://issues.apache.org/jira/browse/JCR-3664
+>             Project: Jackrabbit Content Repository
+>          Issue Type: Task
+>          Components: jackrabbit-jcr-commons
+>            Reporter: Robert Munteanu
+>            Priority: Trivial
+>         Attachments: JCR-3664-1.patch
+>
+>
+> The javadoc for this class is incorrectly formatted - it is written as plain text rather than HTML. It's missing some p and pre tags to make it render as expected.
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrators
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38389-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Thu Sep  5 14:28:56 2013
+Return-Path: <dev-return-38389-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id 35D2E10C43
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Thu,  5 Sep 2013 14:28:56 +0000 (UTC)
+Received: (qmail 20344 invoked by uid 500); 5 Sep 2013 14:28:53 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 20253 invoked by uid 500); 5 Sep 2013 14:28:52 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 20227 invoked by uid 99); 5 Sep 2013 14:28:52 -0000
+Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Sep 2013 14:28:52 +0000
+Date: Thu, 5 Sep 2013 14:28:51 +0000 (UTC)
+From: "Robert Munteanu (JIRA)" <jira@apache.org>
+To: dev@jackrabbit.apache.org
+Message-ID: <JIRA.12667115.1378391071230.85279.1378391331754@arcas>
+In-Reply-To: <JIRA.12667115.1378391071230@arcas>
+References: <JIRA.12667115.1378391071230@arcas>
+Subject: [jira] [Updated] (JCR-3664) FileVault: fix javadoc for
+ PlatformNameFormatter
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 7bit
+X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
+
+
+     [ https://issues.apache.org/jira/browse/JCR-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
+
+Robert Munteanu updated JCR-3664:
+---------------------------------
+
+    Attachment: JCR-3664-1.patch
+    
+> FileVault: fix javadoc for PlatformNameFormatter
+> ------------------------------------------------
+>
+>                 Key: JCR-3664
+>                 URL: https://issues.apache.org/jira/browse/JCR-3664
+>             Project: Jackrabbit Content Repository
+>          Issue Type: Task
+>          Components: jackrabbit-jcr-commons
+>            Reporter: Robert Munteanu
+>            Priority: Trivial
+>         Attachments: JCR-3664-1.patch
+>
+>
+> The javadoc for this class is incorrectly formatted - it is written as plain text rather than HTML. It's missing some p and pre tags to make it render as expected.
+
+--
+This message is automatically generated by JIRA.
+If you think it was sent incorrectly, please contact your JIRA administrators
+For more information on JIRA, see: http://www.atlassian.com/software/jira
+
+From dev-return-38391-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org  Thu Sep  5 17:52:36 2013
+Return-Path: <dev-return-38391-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
+X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
+Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+	by minotaur.apache.org (Postfix) with SMTP id 6107510336
+	for <apmail-jackrabbit-dev-archive@www.apache.org>; Thu,  5 Sep 2013 17:52:36 +0000 (UTC)
+Received: (qmail 8650 invoked by uid 500); 5 Sep 2013 17:52:35 -0000
+Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
+Received: (qmail 8396 invoked by uid 500); 5 Sep 2013 17:52:30 -0000
+Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
+Precedence: bulk
+List-Help: <mailto:dev-help@jackrabbit.apache.org>
+List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
+List-Post: <mailto:dev@jackrabbit.apache.org>
+List-Id: <dev.jackrabbit.apache.org>
+Reply-To: dev@jackrabbit.apache.org
+Delivered-To: mailing list dev@jackrabbit.apache.org
+Received: (qmail 8379 invoked by uid 99); 5 Sep 2013 17:52:28 -0000
+Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Sep 2013 17:52:28 +0000
+X-ASF-Spam-Status: No, hits=4.2 required=5.0
+	tests=HTML_MESSAGE,SPF_NEUTRAL,URI_HEX
+X-Spam-Check-By: apache.org
+Received-SPF: error (athena.apache.org: encountered temporary error during SPF processing of domain of andreas@breakpoint.no)
+Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139)
+    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Sep 2013 17:52:24 +0000
+Received: from [192.168.236.139] (helo=joe.nabble.com)
+	by joe.nabble.com with esmtp (Exim 4.72)
+	(envelope-from <andreas@breakpoint.no>)
+	id 1VHdiA-00021t-MC
+	for dev@jackrabbit.apache.org; Thu, 05 Sep 2013 10:51:18 -0700
+Date: Thu, 5 Sep 2013 10:51:03 -0700 (PDT)
+From: andreas <andreas@breakpoint.no>
+To: dev@jackrabbit.apache.org
+Message-ID: <000501ceaa60$6aa120d0$3fe36270$@breakpoint.no>
+Subject: SV: Jackrabbit JCA and JTA
+MIME-Version: 1.0
+Content-Type: multipart/alternative; 
+	boundary="----=_Part_199642_17401238.1378403463669"
+X-Virus-Checked: Checked by ClamAV on apache.org
+
+------=_Part_199642_17401238.1378403463669
+Content-Type: text/plain; charset=us-ascii
+Content-Transfer-Encoding: 7bit
+
+Hello
+
+It seems like the Jackrabbit session commits independently of the other
+code. I have no idea why. 
+
+ 
+
+Fra: Chris Poulsen [via Jackrabbit]
+[mailto:ml-node+s510166n4659461h46@n4.nabble.com] 
+Sendt: 5. september 2013 09:49
+Til: andreas
+Emne: Re: Jackrabbit JCA and JTA
+
+ 
+
+Hi, 
+
+I don't know about file storing vs. transactions, but I would expect it 
+to work like any other transactional change to the repository. 
+
+Getting the JTA setup correctly can be somewhat of a tricky task - Are 
+you sure that you are in a transaction in your method (and that you are 
+in the correct transaction)? 
+
+Have you tried adding a simple node in the transaction method to see if 
+a simple node is rolled back? Also you can usually ask spring and the 
+JTA provider to produce really detailed logs to help you figure out what 
+is going on. 
+
+HTH. 
+-- 
+Chris 
+
+On 04-09-2013 18:09, andreas wrote: 
+
+
+> Hi 
+> 
+> I am developing an application that uses both Jackrabbit and a database.
+In 
+> Jackrabbit I store the files that I upload, and the database I store all
+the 
+> other data in the app. I am using Spring 3.2, Hibernate 4.x and Jackrabbit
+
+> 2.6.2. I have downloaded the Jackrabbit JCA version and deployed it to
+JBoss 
+> 7.1.1. I have configured it correctly I think. I can upload file to it and
+
+> it is saved. I also debugged my application and I saw that the session 
+> object that invoke save() and logout() on is of type XaSession. I am using
+
+> the datastore. 
+> 
+> The way I tested my code is like this: I have one method in the service 
+> layer of my app annotated with @Transactional. Inside the method I first
+add 
+> a file to the content repository, then I force a RunTimeException to be 
+> thrown (and the code that should run instead of the exception would be to 
+> save my object to the database through Hibernate). I cleared the datastore
+
+> (no files inside it) but when the exception is thrown the file that I
+added 
+> isn't removed from the datastore. 
+> 
+> So, is this correct? Does files in datastore stay in the datastore - not 
+> rolled back? Or should it be removed. I am using the 
+> <tx:jta-transaction-manager /> annotation in Spring config. 
+> 
+> Could someone shed some light over this because I don't understand if I
+got 
+> it working, or if I need to do something else to get it working? And where
+
+> does the metadata of the file that I add get stored? I have configured a
+own 
+> database for the persistence manager but I don't see anything useful in
+the 
+> database tables? There are only a lot of what seems to be binary things 
+> there? Is there a way to verify if a file is inserted or not in the
+database 
+> even though the actual file is stored on disk (datastore)? 
+> 
+> Thank you 
+> 
+> - Andreas 
+> 
+> 
+> 
+> -- 
+> View this message in context:
+http://jackrabbit.510166.n4.nabble.com/Jackrabbit-JCA-and-JTA-tp4659460.html
+> Sent from the Jackrabbit - Dev mailing list archive at Nabble.com. 
+
+
+
+
+
+  _____  
+
+If you reply to this email, your message will be added to the discussion
+below:
+
+http://jackrabbit.510166.n4.nabble.com/Jackrabbit-JCA-and-JTA-tp4659460p4659
+461.html 
+
+To unsubscribe from Jackrabbit JCA and JTA, click here
+<http://jackrabbit.510166.n4.nabble.com/template/NamlServlet.jtp?macro=unsub
+scribe_by_code&node=4659460&code=YW5kcmVhc0BicmVha3BvaW50Lm5vfDQ2NTk0NjB8LTg
+zMDc1MzU4> .
+ 
+<http://jackrabbit.510166.n4.nabble.com/template/NamlServlet.jtp?macro=macro
+_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.Ba
+sicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.templa
+te.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instan
+t_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
+NAML 
+
+
+
+
+
+--
+View this message in context: http://jackrabbit.510166.n4.nabble.com/SV-Jackrabbit-JCA-and-JTA-tp4659467.html
+Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
+------=_Part_199642_17401238.1378403463669
+Content-Type: text/html; charset=us-ascii
+Content-Transfer-Encoding: quoted-printable
+
+<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
+><meta name=3DGenerator content=3D"Microsoft Word 15 (filtered medium)"><!-=
+-[if !mso]><style>v\:* {behavior:url(#default#VML);}
+o\:* {behavior:url(#default#VML);}
+w\:* {behavior:url(#default#VML);}
+.shape {behavior:url(#default#VML);}
+</style><![endif]--><!--[if gte mso 9]><xml>
+<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
+</xml><![endif]--><!--[if gte mso 9]><xml>
+<o:shapelayout v:ext=3D"edit">
+<o:idmap v:ext=3D"edit" data=3D"1" />
+</o:shapelayout></xml><![endif]--><div class=3DWordSection1><p class=3DMsoN=
+ormal><span lang=3DEN-US style=3D'font-size:11.0pt;font-family:"Calibri","s=
+ans-serif";color:#1F497D;mso-fareast-language:EN-US'>Hello<o:p></o:p></span=
+></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt;font=
+-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'>It=
+ seems like the Jackrabbit session commits independently of the other code.=
+ I have no idea why. <o:p></o:p></span></p><p class=3DMsoNormal><span lang=
+=3DEN-US style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color=
+:#1F497D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p class=
+=3DMsoNormal><b><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
+-serif"'>Fra:</span></b><span style=3D'font-size:11.0pt;font-family:"Calibr=
+i","sans-serif"'> Chris Poulsen [via Jackrabbit] [mailto:<a href=3D"/user/S=
+endEmail.jtp?type=3Dnode&node=3D4659467&i=3D0" target=3D"_top" rel=3D"nofol=
+low" link=3D"external">[hidden email]</a>] <br><b>Sendt:</b> 5. september 2=
+013 09:49<br><b>Til:</b> andreas<br><b>Emne:</b> Re: Jackrabbit JCA and JTA=
+<o:p></o:p></span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3D=
+MsoNormal>Hi, <br><br>I don't know about file storing vs. transactions, but=
+ I would expect it <br>to work like any other transactional change to the r=
+epository. <br><br>Getting the JTA setup correctly can be somewhat of a tri=
+cky task - Are <br>you sure that you are in a transaction in your method (a=
+nd that you are <br>in the correct transaction)? <br><br>Have you tried add=
+ing a simple node in the transaction method to see if <br>a simple node is =
+rolled back? Also you can usually ask spring and the <br>JTA provider to pr=
+oduce really detailed logs to help you figure out what <br>is going on. <br=
+><br>HTH. <br>-- <br>Chris <br><br>On 04-09-2013 18:09, andreas wrote: <o:p=
+></o:p></p><div><p class=3DMsoNormal><div class=3D'shrinkable-quote'><br>&g=
+t; Hi <br>&gt; <br>&gt; I am developing an application that uses both Jackr=
+abbit and a database. In <br>&gt; Jackrabbit I store the files that I uploa=
+d, and the database I store all the <br>&gt; other data in the app. I am us=
+ing Spring 3.2, Hibernate 4.x and Jackrabbit <br>&gt; 2.6.2. I have downloa=
+ded the Jackrabbit JCA version and deployed it to JBoss <br>&gt; 7.1.1. I h=
+ave configured it correctly I think. I can upload file to it and <br>&gt; i=
+t is saved. I also debugged my application and I saw that the session <br>&=
+gt; object that invoke save() and logout() on is of type XaSession. I am us=
+ing <br>&gt; the datastore. <br>&gt; <br>&gt; The way I tested my code is l=
+ike this: I have one method in the service <br>&gt; layer of my app annotat=
+ed with @Transactional. Inside the method I first add <br>&gt; a file to th=
+e content repository, then I force a RunTimeException to be <br>&gt; thrown=
+ (and the code that should run instead of the exception would be to <br>&gt=
+; save my object to the database through Hibernate). I cleared the datastor=
+e <br>&gt; (no files inside it) but when the exception is thrown the file t=
+hat I added <br>&gt; isn't removed from the datastore. <br>&gt; <br>&gt; So=
+, is this correct? Does files in datastore stay in the datastore - not <br>=
+&gt; rolled back? Or should it be removed. I am using the <br>&gt; &lt;tx:j=
+ta-transaction-manager /&gt; annotation in Spring config. <br>&gt; <br>&gt;=
+ Could someone shed some light over this because I don't understand if I go=
+t <br>&gt; it working, or if I need to do something else to get it working?=

[... 25305 lines stripped ...]


Mime
View raw message