Re: Next Generation Persistence

Hi, I am currently thinking about a radical solution (you can call it brainstorming): Store the index in a database. This would probably be slower than Lucene, a big disadvantage. Additionally, store data of all workspaces in the same database, using the same connection. Store versions in the sam

[jira] Resolved: (JCR-973) XML import using MacOS X WebDAV client does not work

[ https://issues.apache.org/jira/browse/JCR-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bocanegra resolved JCR-973. -- Resolution: Fixed Committed revision 548395. > XML import using MacOS X WebDAV client does not wo

[jira] Commented: (JCR-973) XML import using MacOS X WebDAV client does not work

[ https://issues.apache.org/jira/browse/JCR-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505865 ] Tobias Bocanegra commented on JCR-973: -- i changed the following: - the xmlhandler does only accept content that hav

[jira] Commented: (JCR-973) XML import using MacOS X WebDAV client does not work

[ https://issues.apache.org/jira/browse/JCR-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505859 ] Bertrand Delacretaz commented on JCR-973: - Note that command-line copies (as opposed to via the Finder GUI) beha

[jira] Created: (JCR-973) XML import using MacOS X WebDAV client does not work

XML import using MacOS X WebDAV client does not work Key: JCR-973 URL: https://issues.apache.org/jira/browse/JCR-973 Project: Jackrabbit Issue Type: Bug Components: webdav Af

Re: Next Generation Persistence

Thomas Mueller wrote: And after a crash, you can re-index everything, then things are consistent and no data is lost (only time is lost). So solving the transactional problem of the index is not highest priority. Still it would be nice to have a clean solution. I agree. IMO the index should be

[GSoC] mu-assessment initial commit

Hello. I commit mu-assessment code to googlecode project hosting. Project can be found at http://code.google.com/p/mu-assessment/ You may check out working copy by svn checkout http://mu-assessment.googlecode.com/svn/trunk/ mu-assessment This code realize only "passing test" scenario. Work is

AW: InvalidItemStateException

hi stefan, thanks for the information ! BR, claus -Ursprüngliche Nachricht- Von: Stefan Guggisberg [mailto:[EMAIL PROTECTED] Gesendet: Montag, 18. Juni 2007 12:50 An: dev@jackrabbit.apache.org Betreff: Re: InvalidItemStateException On 6/18/07, KÖLL Claus <[EMAIL PROTECTED]> wrote: > i g

Re: InvalidItemStateException

On 6/18/07, KÖLL Claus <[EMAIL PROTECTED]> wrote: i get sometimes on an update operation of my node a InvalidItemStateException() with the message 23588706-aaaf-4dc1-b4e6-d78b1c02be6a/{http://www.tirol.gv.at/dms/1.0}size: the item cannot be saved because it has been modified externally. and i d

InvalidItemStateException

i get sometimes on an update operation of my node a InvalidItemStateException() with the message 23588706-aaaf-4dc1-b4e6-d78b1c02be6a/{http://www.tirol.gv.at/dms/1.0}size: the item cannot be saved because it has been modified externally. and i dont know the reason and how i can reproduce it ? can

Re: Journal Maintanence Question

Hi Ian, at the moment, records in the database journal are actually never removed, which enables to create a completely empty repository cluster node that will automatically synchronize to the cluster's state at any point in the future. But, of course, introducing policies that restrict the growt