at first thanks for your reply... i figured out, that "order by @modificationDate" has to be replaced by "order by @lastmodified" - then the order in the resultSet changes ... but the annoying thing is, that the order is just different, but not the one i expected...
i wrote a method that does the order manually by *.getMetaData().getModificationDate(); and i expected that the result would be the same now, but it isnt... :( Maybe "lastmodified" is not the same like "modificationDate" - i thought it would be the same data... if u know more then me ... thx ;) another question @jcr:score: Does anybody know, whether the magnolia search supports jcr:score? I checked some source examples that use jcr-QueryManager and some methods are not implemented in magnolia-QueryManager (or was it in QueryResult?!) e.g. there is only getContent() that gives me a Collection! But there is no getNodes() that gives me an iterator... i dont know whether i try something - that cant work without to write the whole search myself ;-) thx... Marcel Reutegger wrote: > > Are you sure the property name is correct? Please also check the case of > characters. Do the nodes returned by the query actually have a property > modificationDate? > > The query will not fail even if the property is spelled incorrectly or not > present because it may be a residual property or optional. > > regards > marcel > -- View this message in context: http://www.nabble.com/ORDER-BY-clause-in-XPath-Query-using-Magnolia-tf2818077.html#a8145977 Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
