Starting version 6.x, Adobe proposed using Uber Jar to consume any publicly available API of AEM and few other third party APIs. This is the reason your build is failing when you updated the version to 6.0.14, because this version itself is not exposed in Adobe's public repo - https://repo.adobe.com...
That precisely is the reason. for a node to come up as reference in tagManager.find method, it needs to have cq:Taggable mixin. cq:pageContent type node by default has this mixin and hence Page node turns up automatically in .find API call.You can enhance the nodeType definition on your server by mo...
Here is what you need to do:Get com.day.jcr.vault.packaging.Packaging reference injection in your service.Packaging API will get you access to JCRPackageManager i.e. - packaging.getPackageManager(session);Now using PackageManager you can set conflict resolution policy, package name, group, version ...
if you are using a boilerplate approach to maintain all your content for reference component, then here is what you can do;bind activation event listener to activation of just that boiler plate.Refer following article for more details around replication listener - https://helpx.adobe.com/experience-...
It could be a code issue or the issue with link checker that for some reason identifies the links as not reachable. Try disabling the link checker and see if its still the same behavior.You can disable link checking through felix console - http://<ip>:<port>/system/console/configMgr/com.day.cq.rewri...
Rewriting URL is not something that dispatcher controls, rewrite mainly happens because of rewrite module in apache and rules configured.I would suggest you enable rewrite logs in apache to debug level and see why it is issuing a 302 redirect.
if your hashMap keys are not dynamic, then below is what you can do:you can return iterator on first HashMap through your sightly getter method. use data-sly-list.outerHash to iterate over the iterator returned value.Each iteration will give you inner HashMap on object outerHashif you know what are ...
which version of AEM are you using?Also try once by putting your user into administrator or content-authors group if you are not part of any of it and see if it works.-- Runal
Not sure if you have tried this, but finish all the running workflows don't trigger any new ones for some time and block all external excess to your server.Now, go to http://<ip>:<port>/crx/explorer and then make a note of following node /etc/workflow/instances/server0, take a note of all properties...