As a follow up, I found that my OCM query really gives a different order to the (Node instance).getNodes(). getNodes gives them in the correct order, is this a bug?
On Mon, Feb 1, 2010 at 10:17 PM, philip andrew <[email protected]>wrote: > > > Hi, > > I am using the Object Content Manager and ordered nodes, but the results > from the OCM query are not in the same order as the Node query. > What type of query is supposed to give them back in the right order ? It > seems the OCM query does not. > > OCM > http://jackrabbit.apache.org/ocm-search.html > > I registered a node type > > private void registerCmsNodeType(Session session) throws > RepositoryException, IOException { > JackrabbitNodeTypeManager manager = (JackrabbitNodeTypeManager) > session.getWorkspace().getNodeTypeManager(); > // Register the custom node types defined in the CND file > InputStream is = new ByteArrayInputStream(( > "<nt = 'http://www.jcp.org/jcr/nt/1.0'>" + > "[" + Constants.ORSA_CMS_NODE_TYPE + "] > nt:unstructured > orderable").getBytes(Charset.defaultCharset())); > manager.registerNodeTypes(is, > JackrabbitNodeTypeManager.TEXT_X_JCR_CND); > } > > My node. > > > @Node{val jcrType="nt:orsacms_page"} > class OPageNode extends OAbstractNode > { > // Path in the JCR, this seems to be not working? > @BeanProperty > @Field{val path = true} var path:String = _ > > Thanks, Philip > > >
