[jira] Commented: (JCR-569) WorkspaceImporter Refactoring

[ http://issues.apache.org/jira/browse/JCR-569?page=comments#action_12434386 ] Stefan Guggisberg commented on JCR-569: --- Overall I feel this class is circumvoluted and really hard to understand. For instance, the current code contains

bug in SQL Query

I make this query: SELECT * FROM okm:document WHERE jcr:path LIKE '/okm:root/%' OR jcr:path='/okm:root' and this exception is thrown: Invalid combination of jcr:path clauses But the specification says in 8.5.2.2 that this is a valid query (page 289).

Re: Nuclear Fission, Splitting the core: The SPI Effect [was: Improving the accessibility of the Jackrabbit core]

Hi, However, I'm a bit concerned about the revolutionary approach of the SPI effort. Rather than refactoring the Jackrabbit core to better separate the session-local parts, the SPI comes up with a brand new interface contract. This is probably the best thing to do given the SPI goals, but it

[jira] Created: (JCR-570) Fix pom.xml in jackrabbit core (small fix, big return)

Fix pom.xml in jackrabbit core (small fix, big return) -- Key: JCR-570 URL: http://issues.apache.org/jira/browse/JCR-570 Project: Jackrabbit Issue Type: Bug Affects Versions: 1.1

[jira] Updated: (JCR-570) Fix pom.xml in jackrabbit core (small fix, big return)

[ http://issues.apache.org/jira/browse/JCR-570?page=all ] Jukka Zitting updated JCR-570: -- Component/s: maven Affects Version/s: (was: 1.1) Assignee: Jukka Zitting Oh, the JCR jars were uploaded in the Maven repository at

[jira] Commented: (JCR-544) JCR-Server: Workspace.restore not mapped correctly

[ http://issues.apache.org/jira/browse/JCR-544?page=comments#action_12434477 ] angela commented on JCR-544: additional thoughts: what is actually missing in the jcr-server is a distint resource representing the 'workspace'. currently the root node

[jira] Created: (JCR-571) jackrabbit JCA pom.xml

jackrabbit JCA pom.xml -- Key: JCR-571 URL: http://issues.apache.org/jira/browse/JCR-571 Project: Jackrabbit Issue Type: Improvement Affects Versions: 1.1 Environment: maven 2 Reporter: Darren

[jira] Updated: (JCR-571) jackrabbit JCA pom.xml

[ http://issues.apache.org/jira/browse/JCR-571?page=all ] Darren Hartford updated JCR-571: Attachment: pom.xml ahh...attach file on sidebar. Here is the JCA pom.xml jackrabbit JCA pom.xml -- Key: JCR-571

[jira] Commented: (JCR-569) WorkspaceImporter Refactoring

[ http://issues.apache.org/jira/browse/JCR-569?page=comments#action_12434496 ] Nicolas Toper commented on JCR-569: --- Sure. Here it is: Introduction The current o.a.j.core.xml.WorspaceImporter class has one main responsability: to import data

[jira] Commented: (JCR-569) WorkspaceImporter Refactoring

[ http://issues.apache.org/jira/browse/JCR-569?page=comments#action_12434497 ] Nicolas Toper commented on JCR-569: --- Hi Stefan, About your first point, you are right: this is why I sent yesterday a more in depth analysis. This JIRA issue will

[jira] Commented: (JCR-569) WorkspaceImporter Refactoring

[ http://issues.apache.org/jira/browse/JCR-569?page=comments#action_12434503 ] Jukka Zitting commented on JCR-569: --- Nicolas: I would like to create two classes: one generic Importer (name to be defined) and one dedicated to import a

[jira] Resolved: (JCR-571) jackrabbit JCA pom.xml

[ http://issues.apache.org/jira/browse/JCR-571?page=all ] Edgar Poce resolved JCR-571. Resolution: Fixed thanks Darren jackrabbit JCA pom.xml -- Key: JCR-571 URL:

[jira] Updated: (JCR-571) jackrabbit JCA pom.xml

[ http://issues.apache.org/jira/browse/JCR-571?page=all ] Edgar Poce updated JCR-571: --- Component/s: jca updating component jackrabbit JCA pom.xml -- Key: JCR-571 URL: