@jwendling AEM Query builder can be used to query the repository and get
a list of nodes (javax.jcr.node) or hits
(com.day.cq.search.result.Hit)To get specific properties or metadata
from each node, we will have to have custom implementations, via a sling
model/OSGi servlet/OSGi service.Hope this helps.
Hi Kautuk,Thanks for your reply. But I think you got my question wrong.
I am aware of how the orderby predicate works 🙂Let me re-phrase my
issue.This query works well in 6.0. The issue is with 6.1 only.
We are facing an issue with sorting using the query builder API in AEM
6.1.We have a query where sorting happens based on a custom(not cq
default) and this does not work at all in AEM 6.1, while sorting with a
cq default property works. orderby=@jcr:content/newOrder -----> this
does not workorderby=@jcr:content/jcr:title -----------> this worksHas
anyone faced this issue earlier or know the fix for this ? Please help.
We are using Adobe CQ 5.6.1 for our project and we are facing issues
with etc mapping. The attached etc mapping package is the one that we
are using. On trying to resolve and map paths using this in the Sling
Resource Resolver link – /system/console/jcrresolver, resolving and
mapping is happening fine. But in the page, the links are not showing as
mapped URLs. All the links are pointing to full content paths. The same
etc mapping node, when pointed to Geometrixx content path works fine.
There is a way to not cache a few parts of a page alone. Check out the
sling dynamic include, here's the link -
http://www.cognifide.com/blogs/cq/sling-dynamic-include/ Using this, you
can make sure that the component that needs to be dynamic alone does not
get cached. The rest of the page can get cached.Hope this helps!