[jira] Created: (JCR-952) Support lower and upper case functions in order by clause

Components: query Affects Versions: 1.3 Reporter: James Hang Priority: Minor The query languages should support lower- and upper-case functions within the order by clause. This would provide case-insensitive ordering of query results. Example: Find all nt:base nodes

[jira] Created: (JCR-887) DateField class should be public

Reporter: James Hang Priority: Minor Fix For: 1.3 The class org.apache.jackrabbit.core.query.lucene.DateField should be made public. It has several public methods which are useful but are currently not accessible because the class itself is not accessible outside of its

DateField class should be public

Is there a reason why the org.apache.jackrabbit.core.query.lucene.DateField class is not public (even though its methods are public)? All the other type Field classes are public (LongField, DoubleField, etc.). James -- View this message in context:

Re: Lucene index

Reutegger wrote: Hi James, James Hang wrote: After spending some time running Jackrabbit in debug mode, I noticed some peculiar behavior in the Lucene SearchIndex implementation. When indexing of a Node occurs via the AbstractIndex.addDocument() method, the Lucene Document object being

Lucene index

After spending some time running Jackrabbit in debug mode, I noticed some peculiar behavior in the Lucene SearchIndex implementation. When indexing of a Node occurs via the AbstractIndex.addDocument() method, the Lucene Document object being indexed seems to contain all the indexed fields,

TCK tests

Hi, We are trying to run the TCK tests in the jackrabbit-tests project, but getting failures mostly related to missing nodetypes test:versionable and test:refTargetNode. Are the tests expecting these nodetypes to already exist in your repository? If so, is there a cnd file that contains these

jcr navigator contrib project

Hi, Is anyone using the jcr navigator contrib project? We've gotten it to come up and mostly working. Navigating through the repository works just fine. The only problem we're having is when we try to use some of the menu options like Add Node. The dialog box comes up, but whenever you hit

Escaping node names in xpath queries

We're having problems running an xpath query where a node name in the xpath contains blank spaces. For example, the following query won't work because of the blank space in the name Node A: /jcr:root//mypath/Node A//element(*, myType) order by @cx:created ascending We tried uri encoding the

Xpath queries containing blank spaces and a period

We're having problems running an xpath query where a node name in the xpath contains a blank space followed by a period . in the name. For example, the following query fails: /jcr:root//mypath/My Document.txt//element(*, myType) order by @cx:created ascending It throws this exception:

Re: Apache Jackrabbit 1.2 release plan

I assume that the change for JCR-545 only allows reregistering nodetypes with trivial modiciations? So it would still throw a RepositoryException(not yet implemented) for non-trivial changes? -- View this message in context:

Re: exception in indexer when creating versionable node

I am getting the exact error when saving versionable nodes. Restarting the repository also fixes it for me. This happened after I upgraded to 1.1 from 1.0.1. My unit tests, however, are all passing. I just get this error in the logs. Carlos Villegas wrote: Hi, I just upgraded