@smacdonald2008Sorry, this was a shorthand from my side. Yes, I'm aware of ExtJS still existing in Classing UI, but the preference is to migrate to TouchUI. Therefore the question@Sham HCI'm worried that I misunderstood you, so let me rephrase: are you saying you are already planning to migrate this...

For the previous version of CQ/AEM the ExtJS with the pathfield widget user was able to both: typeahead the path and select it from the tree browser.In the brand new AEM6 ExtJS has been dropped in favour of Coral UI. I've found some examples of pathfield input, but there is no tree selection possibi...

I've noticed some problems with the vanity paths register in AEM6. Please take a look into the Resource Resolver status page in OSGi console: /system/console/jcrresolver and try to find the mapping that have been created based on your vanityPath. For a simple /mypath it should be sth similar to ^[^/...

To meet the requirements I have implemented a custom nodetype that is placed inside the bundle within a package. The nodetype is used at the same time by a content that is also available in the same package.The problem is, while installing the package for the very first time on the instance, the nod...

Try out SlingRequestProcessor class:@Reference SlingRequestProcessor slingRequestProcessor; slingRequestProcessor.processRequest(HttpServletRequest request, HttpServletResponse response, ResourceResolver resourceResolver)You need to create mock request and response objects. You might want to have a ...