Re: namespace resolution error

On 4/26/06, Brian Moseley [EMAIL PROTECTED] wrote: i'm having an odd problem looking up a property. the exception is: javax.jcr.RepositoryException: failed to resolve path cosmo:username relative to /r/ro/root: cosmo: cosmo at

[jira] Created: (JCR-415) Enhance indexing of binary content

Enhance indexing of binary content -- Key: JCR-415 URL: http://issues.apache.org/jira/browse/JCR-415 Project: Jackrabbit Type: Improvement Components: indexing Versions: 1.0, 0.9 Reporter: Marcel Reutegger

Re: Restricting xpath query to document text

thomasg wrote: How can I modify the query to return hits when the word is in the document body and not if it is just in one of the properties? with the current implementation the only way to achieve this is to prohibit the term in another clause for the excluded properties. currently the

Re: Restricting xpath query to document text

Thanks for your reply. To clarify the situation at little. I was expecting to run a query such as: //element(*, axxia:resource)[jcr:contains(@jcr:data, 'classes')] to only search the contents of a document. This does not currently return an expected hit. Will resolving the issue JCR-415 refered

[jira] Resolved: (JCR-411) Binding repository to a nameserver with RegistryHelper causes failure on lookup.

[ http://issues.apache.org/jira/browse/JCR-411?page=all ] Stefan Guggisberg resolved JCR-411: --- Fix Version: 1.0.1 Resolution: Fixed fixed in svn rev. 397583 thanks for reporting this issue! Binding repository to a nameserver with

RE: Simple queries failing

Hi David, If you check out the JCR spec in section 6.6.4.3 (Context Node) it says that every Xpath query must start with the pseudo-root context node named jcr:root. To quote: The context node of an XPath query is the XML node relative to which the query expression is evaluated. A relative

CND x XML compatibility for custom node definition.

In the following xml definition: nodeType name=xxx:base isMixin=false hasOrderableChildNodes=false primaryItemName= supertypes supertypent:hierarchyNode/supertype /supertypes propertyDefinition name=prop:creator requiredType=Reference autoCreated=false

Is the xpath 'union' operator supported in jackrabbit?

Is the xpath 'union' operator supported in jackrabbit? For example, /jcr:root/a/b/[EMAIL PROTECTED]bar] union /jcr:root/a/c/[EMAIL PROTECTED]bar].or must this be done using 2 separate queries and merged by the user? It appears I can use SQL with the jcr:path and the or conjunction to get