On 28.05.2015, at 23:07, Carsten Ziegeler <[email protected]> wrote: >> No, it's both. It is a normal API [1], usage example at [2], but it also has >> a form that is easy to transport over http using GET/POST parameters and >> comes with a (popular) servlet that provides the result as json. The general >> predicate format is not depending on an order or correctly nested brackets, >> so you can easily build "advanced" search forms. >> >> [1] >> https://docs.adobe.com/docs/en/aem/6-0/develop/ref/javadoc/com/day/cq/search/package-summary.html >> [2] >> https://docs.adobe.com/docs/en/aem/6-0/develop/ref/javadoc/com/day/cq/search/QueryBuilder.html >> > Right but it's JCR based, any plans on basing this on resources?
It converts into a JCR xpath query, yes. But other than that it gives both JCR (Node) and Resource API (Resource) in the search result hits for convenience. Nothing that should be a problem. Moving it to Sling would mean a few changes anyway, while keeping it backwards compatible on the query statement side. Cheers, Alex
