[jira] Commented: (JCR-989) Modify LazyQueryResultImpl to allow resultFetchSize to be set programmatically

2007-06-29 Thread Christoph Kiehl (JIRA)
[ https://issues.apache.org/jira/browse/JCR-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509209 ] Christoph Kiehl commented on JCR-989: - To be honest I don't like this generic setOption() method. Methods like that

Re: Less flexibility

2007-06-29 Thread Christoph Kiehl
Thomas Mueller wrote: I am also for making it less configurable. For my current project (GlobalDataStore), dead code and deprecated interfaces are quite a pain. I would also remove unused persistence managers, and code that we know is not tested well. +1 There are from time to time users on t

Re: Less flexibility

2007-06-29 Thread Christoph Kiehl
Jukka Zitting wrote: * Bundle persistence is in almost all cases more efficient than the previous item persistence where each node and property is stored separately. But the bundle persistence manager still needs to explicitly simulate item persistence to comply with the PersistenceManager inter

[jira] Updated: (JCR-993) corrupted paths after moving nodes

2007-06-29 Thread Stefan Rinner (JIRA)
[ https://issues.apache.org/jira/browse/JCR-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Rinner updated JCR-993: -- Attachment: JackrabbitPathProb.java simple testcase > corrupted paths after moving nodes > --

[jira] Created: (JCR-993) corrupted paths after moving nodes

2007-06-29 Thread Stefan Rinner (JIRA)
corrupted paths after moving nodes -- Key: JCR-993 URL: https://issues.apache.org/jira/browse/JCR-993 Project: Jackrabbit Issue Type: Bug Affects Versions: 1.3 Reporter: Stefan Rinner we just

Re: corrupted paths after moving nodes

2007-06-29 Thread Stefan Guggisberg
hi stefan, On 6/29/07, Stefan Rinner <[EMAIL PROTECTED]> wrote: Hi we just found a bug which corrupts the results of Node.getPath() - it seems to be related to older Jackrabbit bugs (e.g. JCR-768) but still happens in jackrabbit 1.3 and jackrabbit-1.4-SNAPSHOT Basically we have a node with 3 s

Re: Less flexibility

2007-06-29 Thread Thomas Mueller
Hi, I am also for making it less configurable. For my current project (GlobalDataStore), dead code and deprecated interfaces are quite a pain. I would also remove unused persistence managers, and code that we know is not tested well. Thomas On 6/29/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:

corrupted paths after moving nodes

2007-06-29 Thread Stefan Rinner
Hi we just found a bug which corrupts the results of Node.getPath() - it seems to be related to older Jackrabbit bugs (e.g. JCR-768) but still happens in jackrabbit 1.3 and jackrabbit-1.4-SNAPSHOT Basically we have a node with 3 subnodes (a, b, c), we move all of them to index 1 - this wo

Re: Less flexibility

2007-06-29 Thread Jukka Zitting
Hi, On 6/29/07, Felix Meschberger <[EMAIL PROTECTED]> wrote: Yet, another problem you are actually bringing up is the configuration of Jackrabbit at large: I think the current way of configuring Jackrabbit is not flexible enough and needs a rework, too (hasn't this been said before :-) ). Maybe

Re: Less flexibility

2007-06-29 Thread Felix Meschberger
Hi Jukka, I agree that these internal interfaces - particularly PeristenceManager comes to my mind - we initially created to solve problems at a very early stage of Jackrabbit development. Later they gained momentum and span off their own life in a way, they were never intended to be used. As suc

Less flexibility

2007-06-29 Thread Jukka Zitting
Hi, I think this will be a bit controversial, but I would like to explore options for making Jackrabbit *less* flexible and configurable. Currently we have quite a few internal interfaces like PersistenceManager, QueryHandler, FileSystem, and Journal that allow you to fully configure various par

[jira] Commented: (JCR-989) Modify LazyQueryResultImpl to allow resultFetchSize to be set programmatically

2007-06-29 Thread Marcel Reutegger (JIRA)
[ https://issues.apache.org/jira/browse/JCR-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509110 ] Marcel Reutegger commented on JCR-989: -- > QueryImpl is located in org.apache.jackrabbit.core.query and is not lucen

[jira] Resolved: (JCR-992) Improve Performance of DescendantSelfAxisQuery

2007-06-29 Thread Marcel Reutegger (JIRA)
[ https://issues.apache.org/jira/browse/JCR-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-992. -- Resolution: Fixed Fix Version/s: 1.4 Thanks a lot for the patch. Looks good. I only renamed

[jira] Commented: (JCR-989) Modify LazyQueryResultImpl to allow resultFetchSize to be set programmatically

2007-06-29 Thread Christoph Kiehl (JIRA)
[ https://issues.apache.org/jira/browse/JCR-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509106 ] Christoph Kiehl commented on JCR-989: - QueryImpl is located in org.apache.jackrabbit.core.query and is not lucene s

[jira] Commented: (JCR-989) Modify LazyQueryResultImpl to allow resultFetchSize to be set programmatically

2007-06-29 Thread Marcel Reutegger (JIRA)
[ https://issues.apache.org/jira/browse/JCR-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509104 ] Marcel Reutegger commented on JCR-989: -- Thank you for the patch. Wouldn't it be more intuitive to set the resultFe

[jira] Resolved: (JCR-962) Deadlocks in ConcurrentVersioningWithTransactionsTest

2007-06-29 Thread Marcel Reutegger (JIRA)
[ https://issues.apache.org/jira/browse/JCR-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-962. -- Resolution: Fixed Fix Version/s: 1.4 Assuming lazy consensus I committed the patch in revis

RE: Jackrabbit press release

2007-06-29 Thread Frédéric Esnault
-Message d'origine- De : Jukka Zitting [mailto:[EMAIL PROTECTED] Envoyé : vendredi 29 juin 2007 13:30 À : dev@jackrabbit.apache.org Objet : Re: Jackrabbit press release > Personally I find milestones in this process to be > much more interesting and newsworthy than reaching a plateau wher

Re: Jackrabbit press release

2007-06-29 Thread Jukka Zitting
Hi, On 6/29/07, Frédéric Esnault <[EMAIL PROTECTED]> wrote: But I agree making so noise about the 1.4 could attract some more eyes-and-brains on the project. An another big release with fireworks, beers and girls for the 2.0? Big +1 to anything that attracts fireworks, beers, and boys or gir

Re: Jackrabbit press release

2007-06-29 Thread Jukka Zitting
Hi, On 6/29/07, Frédéric Esnault <[EMAIL PROTECTED]> wrote: About 1.4 release of Jackrabbit, I'm less enthusiastic, because I think some issues should definitely be addressed, or at least discussed and if the decision is to do nothing about them (yet), some damn good reasons should be found and

RE: Jackrabbit press release

2007-06-29 Thread Frédéric Esnault
I was not saying Jackrabbit had to be perfect, of course ;) I was referring to Jukka's introduction about apache products and press releases : "some major new stuff to be announced beyond the normal technical audience". And my interpretation is that it should be big enough to : 1. attract more pe

Re: Jackrabbit press release

2007-06-29 Thread Bertrand Delacretaz
On 6/29/07, Frédéric Esnault <[EMAIL PROTECTED]> wrote: ...About 1.4 release of Jackrabbit, I'm less enthusiastic, because I think some issues should definitely be addressed... I don't think Jackrabbit has to be perfect to warrant a press release. Quite the contrary in fact, attracting more

RE: Jackrabbit press release

2007-06-29 Thread Frédéric Esnault
Hi Jukka ! First of all, let me say that I think Jackrabbit 2.0 release would be a perfect reason for going public (press). I mut admit I didn't really had a deep look into the 2.0 features and improvements compared to 1.3 (and 1.4), but I guess there is some good reason to enjoy (I'll check t

Jackrabbit press release

2007-06-29 Thread Jukka Zitting
Hi, Apache projects can issue formal press releases when there are some major new stuff to be announced beyond the normal technical audience. Press releases are a good way to generate interest within the press, analysts, and other similar audiences. Jackrabbit 2.0 with JCR 2.0 support will defin

[jira] Resolved: (JCR-991) Queries 'see' added nodes within repository before being persisted, not allowed according to spec (6.6.12)

2007-06-29 Thread Marcel Reutegger (JIRA)
[ https://issues.apache.org/jira/browse/JCR-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-991. -- Resolution: Cannot Reproduce When I run the test it prints: ni count =1 Found node using getNode(