rainer wrote:
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...
What's the property type of @lastmodified? If it is a String representation of a
date and the lexicographical order of the representation does not match the
natural order of dates you may get confusing results.
i wrote a method that does the order manually by
*.getMetaData().getModificationDate();
??? This does not seem to be a method of the JCR API nor Jackrabbit.
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 ;)
Maybe someone on the magnolia list can help you here? I've no idea where those
properties belong to.
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 ;-)
This rather seems to be a magnolia question.
regards
marcel
