[jira] Updated: (JCR-731) Can the caching mechanism be improved?

[ https://issues.apache.org/jira/browse/JCR-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martijn Hendriks updated JCR-731: - Attachment: CachingTest.java > Can the caching mechanism be improved? >

[jira] Commented: (JCR-731) Can the caching mechanism be improved?

[ https://issues.apache.org/jira/browse/JCR-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472398 ] Martijn Hendriks commented on JCR-731: -- Stefan, thanks for your feedback! I agree that using the exception mechani

[jira] Created: (JCR-741) Handling of multiple residual prop defs in EffectiveNodeTypeImpl

Handling of multiple residual prop defs in EffectiveNodeTypeImpl Key: JCR-741 URL: https://issues.apache.org/jira/browse/JCR-741 Project: Jackrabbit Issue Type: Bug C

[jira] Created: (JCR-740) Support for the decendant-or-self axis in XPath predicates

Support for the decendant-or-self axis in XPath predicates -- Key: JCR-740 URL: https://issues.apache.org/jira/browse/JCR-740 Project: Jackrabbit Issue Type: Improvement Compo

Re: Strange behavior on upgrade from 1.1.1 to 1.2.1

Savas Triantafillou wrote: I have stopped jackrabbit, replaced all necessary jars , deleted repository home directory not only the index dirs and started jackrabbit I just tried exactly the same and queries worked fine with content I added. This way queries did not work at all this is very

[jira] Commented: (JCR-322) Support node type modification and removal

[ https://issues.apache.org/jira/browse/JCR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472288 ] Anton Slutsky commented on JCR-322: --- I'm thinking, there are basically two alternatives here. Either we expose the

Re: Strange behavior on upgrade from 1.1.1 to 1.2.1

I have stopped jackrabbit, replaced all necessary jars , deleted repository home directory not only the index dirs and started jackrabbit This way queries did not work at all, whereas if I delete only the index files as you mention in http://issues.apache.org/jira/browse/JCR-669 , everything wor

Re: Jackrabbit query performance issues

Hi Savas, Savas Triantafillou wrote: 1. As you may see in the following queries, I would like to load all nodes of a certain type using several forms The first one provides no information about the root path of the nodes, nor any information about their name DEBUG - QueryImpl

[jira] Commented: (JCR-247) Child axis support for XPath predicates

[ https://issues.apache.org/jira/browse/JCR-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472255 ] Marcel Reutegger commented on JCR-247: -- No, this is not supported. Only support for the child axis was added not fo

Re: Strange behavior on upgrade from 1.1.1 to 1.2.1

Savas Triantafillou wrote: Old index contains a file named ns_mapping.properties inside index directory where new index contains a file ns_idx.properties inside namespaces directories and ns_mapping.proeprties does not exists Somehow if these two files exists at the same time queries upon old

Re: Concurrent Node Modification using Locked utility class causes issues

vijay s wrote: Problem: I am able to get my application working with the Locked utility class, but I believe the locking of the folder to add content is causing some issues when I try to "concurrently" add many nodes to a single folder. Jackrabbit throws a random ItemNotFoundException after I

Re: Strange behavior on upgrade from 1.1.1 to 1.2.1

Old index contains a file named ns_mapping.properties inside index directory where new index contains a file ns_idx.properties inside namespaces directories and ns_mapping.proeprties does not exists Somehow if these two files exists at the same time queries upon old nodes are impossible Restru

Re: Strange behavior on upgrade from 1.1.1 to 1.2.1

An upgrade from 1.1.1 to 1.2.1 does not require to re-arrange the repository home directories nor does it required to re-index the workspaces. just replacing the jar files should be sufficient. regards marcel Savas Triantafillou wrote: FYI, I think I have solved the problem but I need to ru

Re: Searching "&" character

Julian Reschke wrote: "&" is not reserved in XPath, but in XML. Thus, I wouldn't expect it to be reserved in JCR's XPath language as well. Thus, "Dolce&Gabbana" in a query expression should match "Dolce&Gabbana" in content. If it doesn't, that is likely a bug that needs to be fixed. Julian i

[jira] Resolved: (JCR-739) String literal must not interpret entity references

[ https://issues.apache.org/jira/browse/JCR-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-739. -- Resolution: Fixed Changed the strip.xsl to special-case the StringLiteral token and ignore the en

[jira] Updated: (JCR-739) String literal must not interpret entity references

[ https://issues.apache.org/jira/browse/JCR-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-739: - Description: The ampersand character in a string literal is interpreted as a start character for an