[jira] [Resolved] (JCR-3528) Node type selection for CanAddChildNodeCallWithNodeTypeTest#testResidualAndLegalType is not optimal

2013-03-05 Thread Alex Parvulescu (JIRA)
[ https://issues.apache.org/jira/browse/JCR-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu resolved JCR-3528. -- Resolution: Fixed Fix Version/s: 2.7 Thanks Jukka for the feedback! fixed with rev

[jira] [Created] (JCR-3529) Property2Index: node type is ignored

2013-03-05 Thread Thomas Mueller (JIRA)
Thomas Mueller created JCR-3529: --- Summary: Property2Index: node type is ignored Key: JCR-3529 URL: https://issues.apache.org/jira/browse/JCR-3529 Project: Jackrabbit Content Repository Issue

Manually Giving Access Right on Derby Database

2013-03-05 Thread Vikas . Aggarwal
Hi, Can you please let me know that can we manually give permission to the document stored in the Derby Database. If yes, can you please tell me the procedure to do it. There is the situation where the user who has created the document has being deleted. So there is a need to assign relevant

Consistency aka Isolation Level (was: OAK-638 Avoid branch/merge for small commits)

2013-03-05 Thread Marcel Reutegger
Hi, I think it's better to discuss on the mailing list instead of an already closed issue... Michael wrote: It should be possible to combine this with the branch, rebase, fast forward merge approach I described above : we just need to make the fast forward merge a bit more clever such that it

Re: Consistency aka Isolation Level (was: OAK-638 Avoid branch/merge for small commits)

2013-03-05 Thread Michael Dürig
On 5.3.13 9:27, Marcel Reutegger wrote: Hi, I think it's better to discuss on the mailing list instead of an already closed issue... Michael wrote: It should be possible to combine this with the branch, rebase, fast forward merge approach I described above : we just need to make the fast

Re: enter() method for JCR implementation classes

2013-03-05 Thread Michael Dürig
On 5.3.13 9:56, Jukka Zitting wrote: Just some anecdotal evidence: a single call to Node.addNode() results in a call to Node.getPrimaryNodeType() which in turn ends up calling Property.getValue() and which eventually results in a call to Property.isMultiple(). So there will be quite a bit of