[jira] [Commented] (JCR-2950) CachingEntryCollector ineffective if number of accessed policies exceeds cache size

[ https://issues.apache.org/jira/browse/JCR-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192995#comment-13192995 ] Julian Reschke commented on JCR-2950: - Should we try to make the cache work concurrently

[jira] [Commented] (JCR-2638) Litmus locks test failures

[ https://issues.apache.org/jira/browse/JCR-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193008#comment-13193008 ] Julian Reschke commented on JCR-2638: - For the current trunk I get: -> running `locks':

[jira] [Closed] (JCR-2541) spi2dav : EventJournal not implemented

[ https://issues.apache.org/jira/browse/JCR-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting closed JCR-2541. -- > spi2dav : EventJournal not implemented > --- > > K

[jira] [Updated] (JCR-3216) When fetching node ids in checks for the checker all queries should use the same ordering

[ https://issues.apache.org/jira/browse/JCR-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-3216: --- Fix Version/s: (was: 2.5) > When fetching node ids in checks for the checker all queries should

[jira] [Updated] (JCR-406) If header evaluation compliance problems

[ https://issues.apache.org/jira/browse/JCR-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-406: --- Component/s: jackrabbit-jcr-server > If header evaluation compliance problems >

[jira] [Updated] (JCR-3209) lock token validity

[ https://issues.apache.org/jira/browse/JCR-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-3209: --- Issue Type: Improvement (was: Task) Do we want to include this already in 2.4? Seems like a relatively

[jira] [Updated] (JCR-3218) UserImporter should trigger execution AuthorizableActions in case of user/group creation

[ https://issues.apache.org/jira/browse/JCR-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-3218: --- Fix Version/s: (was: 2.3.7) 2.4 Merged to the 2.4 branch in revision 1235741.

[jira] [Updated] (JCR-3220) simple webdav server does not support lock timeouts

[ https://issues.apache.org/jira/browse/JCR-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-3220: --- Affects Version/s: 2.3.7 Fix Version/s: (was: 2.6) 2.4 Merged to the

[jira] [Updated] (JCR-3214) [Lock] weird number for "infinite"

[ https://issues.apache.org/jira/browse/JCR-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-3214: --- Fix Version/s: (was: 2.6) 2.4 Merged to the 2.4 branch in revision 1235746.

[jira] [Commented] (JCR-3209) lock token validity

[ https://issues.apache.org/jira/browse/JCR-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193048#comment-13193048 ] Julian Reschke commented on JCR-3209: - it's both low-risk and low-prio, so it might be s

[jira] [Updated] (JCR-3148) Using transactions still leads to memory leak

[ https://issues.apache.org/jira/browse/JCR-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-3148: --- Fix Version/s: 2.2.11 Merged to the 2.2 branch in revision 1235755. > Using transactio

[jira] [Updated] (JCR-3167) Make Jackrabbit compile on Java 7

[ https://issues.apache.org/jira/browse/JCR-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-3167: --- Fix Version/s: 2.2.11 Merged to the 2.2 branch in revision 1235761. > Make Jackrabbit

[jira] [Updated] (JCR-3174) Destination URI should be normalized

[ https://issues.apache.org/jira/browse/JCR-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-3174: --- Affects Version/s: 2.2.10 Fix Version/s: 2.2.11 Merged to the 2.2 branch in revision 1235779.

[jira] [Updated] (JCR-3175) InputContextImpl: cannot upload file larger than 2GB

[ https://issues.apache.org/jira/browse/JCR-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-3175: --- Affects Version/s: (was: 2.4) 2.2.10 2.3.5 Fix

[jira] [Updated] (JCR-3210) NPE in spi2dav when server does not send all headers

[ https://issues.apache.org/jira/browse/JCR-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-3210: --- Affects Version/s: (was: 2.3.5) 2.2.10 2.3.6 F

Build failed in Jenkins: Jackrabbit-2.2 #57

See Changes: [jukka] 2.2: Merged revision 1232100 (JCR-3210) [jukka] 2.2: Merged revision 1213276 (JCR-3175) [jukka] 2.2: Merged revision 1213289 (JCR-3174) [jukka] 2.2: Merged revision 1209581 (JCR-3167) [jukka] 2.2: Merged revision 1

Re: Build failed in Jenkins: Jackrabbit-2.2 #57

Hi, On Wed, Jan 25, 2012 at 5:10 PM, Apache Jenkins Server wrote: > Jan 25, 2012 4:10:54 PM hudson.remoting.Channel$ReaderThread run > SEVERE: I/O error in channel channel > java.io.StreamCorruptedException >        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1332) >        at

[jr3 Microkernel] semantics of revisionId in commit method

Hi, Microkernel.commit() has a revisionId parameter. Could someone (Stefan?) clarify the semantics of this parameter? The Javadoc only says "revision the changes are based on". But it fails to explain the actual effect of that parameter. Michael

[jira] [Updated] (JCR-2406) Upgrade httpclient dependency to 4.0

[ https://issues.apache.org/jira/browse/JCR-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-2406: Component/s: jackrabbit-jcr-server Affects Version/s: (was: 2.0-beta1) > Upgrade ht

[jira] [Updated] (JCR-3186) Export size of Observation eventQueue to JMX

[ https://issues.apache.org/jira/browse/JCR-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3186: Assignee: (was: Julian Reschke) > Export size of Observation eventQueue to JMX >

[jr3 Microkernel] how should we handle failed save operations?

Hi, In an earlier discussion (probably offline), we decided to not implement Item.refresh() since it doesn't go well with the MVCC model jr3 is based on. Furthermore, JCR doesn't have an Item.undo() method for undoing changes. This may lead to problems when a Session.save() fails due to the