Re: Jackrabbit fails to start if database user is not schema owner

On Thu, Mar 12, 2009 at 2:40 PM, Martijn Hendriks wrote: > The tables already existed. The testcase is this: > * Start Jackrabbit the regular way which you describe (Jackrabbit autocreates > the tables). > * Stop Jackrabbit > * Change the user credentials in the repository.xml to those of a user

[jira] Commented: (JCR-2014) Jcr2Spi: Warning upon reloading property values

[ https://issues.apache.org/jira/browse/JCR-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681444#action_12681444 ] Michael Dürig commented on JCR-2014: Looks good to me. Thanks for fixing. > Jcr2Spi: War

jackrabbit-core 1.4.10 release plan

Hi, It looks like we at Day still need some fixes backported into another 1.4.x release of jackrabbit-core, so I've created the "core-1.4.10" target in Jira in preparation for the jackrabbit-core 1.4.10 release. Please use that to tag the issues to be included. I'll cut the release candidate some

RE: Jackrabbit fails to start if database user is not schema owner

The tables already existed. The testcase is this: * Start Jackrabbit the regular way which you describe (Jackrabbit autocreates the tables). * Stop Jackrabbit * Change the user credentials in the repository.xml to those of a user with only data manipulation rights. * Start Jackrabbit again -> thi

[jira] Updated: (JCR-2004) Update SPI locking to match JCR 2.0

[ https://issues.apache.org/jira/browse/JCR-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated JCR-2004: Attachment: JCR-2004_spi.patch > Update SPI locking to match JCR 2.0 > --- > >

Re: Jackrabbit fails to start if database user is not schema owner

On Thu, Mar 12, 2009 at 2:23 PM, Martijn Hendriks wrote: > Hi, > > One of our customers has strict rules for DB access: the application can only > do data manipulation, which means that the database user configured in > Jackrabbit's repository.xml is not the schema owner. Of course, Jackrabbit

RE: Jackrabbit 1.5.5 release plan

Hi Jukka, It would be nice if JCR-1117 could be part of 1.5.5. Best regards, Martijn > -Original Message- > From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] > Sent: Thursday, March 12, 2009 12:16 PM > To: Jackrabbit Developers > Subject: Jackrabbit 1.5.5 release plan > > Hi, > > O

Jackrabbit fails to start if database user is not schema owner

Hi, One of our customers has strict rules for DB access: the application can only do data manipulation, which means that the database user configured in Jackrabbit's repository.xml is not the schema owner. Of course, Jackrabbit can then only start if the schema is already present in the DB. The

[jira] Resolved: (JCR-2021) WebDAV: add support for DAV:lockroot

[ https://issues.apache.org/jira/browse/JCR-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela resolved JCR-2021. - Resolution: Fixed > WebDAV: add support for DAV:lockroot > > >

[jira] Created: (JCR-2021) WebDAV: add support for DAV:lockroot

WebDAV: add support for DAV:lockroot Key: JCR-2021 URL: https://issues.apache.org/jira/browse/JCR-2021 Project: Jackrabbit Content Repository Issue Type: Improvement Components: jackrabbit-webda

[jira] Resolved: (JCR-2009) Large file download over webdav causes exception

[ https://issues.apache.org/jira/browse/JCR-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela resolved JCR-2009. - Resolution: Fixed Fix Version/s: 1.5.5 fixed as suggested (just added minor modifications and a simple test)

Jackrabbit 1.5.5 release plan

Hi, On Thu, Mar 12, 2009 at 12:07 PM, Jukka Zitting wrote: > Any other changes should wait for 1.5.5. Since we already have a few candidates like JCR-1216, I think we should do the 1.5.5 release in near future. In preparation for the release I've now created the 1.5.5 tag in Jira. Feel free to u

Re: Jackrabbit 1.5.4 release plan (Was: [VOTE] Release Apache Jackrabbit 1.5.3)

Hi, On Thu, Feb 26, 2009 at 11:13 AM, Jukka Zitting wrote: > However, I'd like to only include minimum risk fixes in 1.5.4 as 1.5.3 > was quite heavily tested and I don't want to invalidate those tests > for 1.5.4 by making too many changes. Just to keep everyone on the same page, the 1.5.4 rele

[jira] Updated: (JCR-1216) Unreferenced sessions should get garbage collected

[ https://issues.apache.org/jira/browse/JCR-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-1216: --- Fix Version/s: (was: 1.6.0) 1.5.5 OK, seems reasonable. Scheduling this for incl

[jira] Resolved: (JCR-1216) Unreferenced sessions should get garbage collected

[ https://issues.apache.org/jira/browse/JCR-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-1216. - Resolution: Fixed Fix Version/s: 1.6.0 Committed in revision 752831 (trunk). This is definit

[jira] Commented: (JCR-1216) Unreferenced sessions should get garbage collected

[ https://issues.apache.org/jira/browse/JCR-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681255#action_12681255 ] Stefan Guggisberg commented on JCR-1216: > Hopefully the final patch. Using WeakRefer

[jira] Updated: (JCR-1216) Unreferenced sessions should get garbage collected

[ https://issues.apache.org/jira/browse/JCR-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-1216: Attachment: referencePatch.txt Hopefully the final patch. Using WeakReferences again. > Unreferenced