I added a servlet filter and used a wrapper to wrap the response as
my sling servler filter options, I used the same resource types and
extensions as defined in my model/exporter annotations
This looks easy enough (it's not far from the gzipping code that I had
in my original servlets), but I dont know where I would place this code.
I don't see a place in the exporter to actually write out the response
I recently converted a set of json generating servlets to use the
jackson sling model exporter. Previously, I used gzip encoding and wrote
the http entity with a gzip writer after I had constructed the json
objects myself--not a very fun or concise process. I am thrilled with
the clarity and brevity...
HI Arun, Apologies for not being clear. We want more or less a "best
match" that would first sort by # tags matched, then a subsort by
display date 1st sort: # of matching tags desc 2nd sort: display date
desc For 7 stories: Story A: tags: a,c | displayDate: 4/1/22 Story B:
tags: a,b,c | displayDate...
Hi Everyone, I am working on a project improving the search results for
a "related stories" component in our news system. Here is a simplified
query that shows how our current search functions.
We have recently upgraded (via migration) to 6.4 from 6.2 and are
getting some new nodetransition emails when users who have replicate
rights to a page that contains assets that they don't have replicate
rights to try to activate. In many cases, the assets on the page have
been previously activated,...
Here's the only error that I'm seeing. "com.day.cq.search" and
"org.apache.jackrabbit.oak.query" both remain empty, which suggests to
me that it doesn't get to generating the xpath query. This is also
suggersted by the fact that the querybuilder debugger doesn't generate
an xpath query..22.03.2019 1...
This doesn't address the problem, which I think has more to do with the
processing and transformation of the querybuilder version of the query
into xpath or something else--updating those values (doubling them) did
not solve the problem.The query never gets to run, as far as I can tell.
We recently updated to 6.4 and I'm working on making our systems forward
compatible. For the most part I've been successful, but it seems that
the query builder can not handle large, complicated queries such as the
one below, typical of a search in our news system.I've found that I can
run this and ...