AEM understands touch/classic view

Hi

Please have a look at the explanation:-  

1. Let the URL be:- http://localhost:4502/editor.html/content/we-retail.html   (i.e. http://localhost:4502/editor.html/.... )
2. Request processing will start resource resolution, there in the URL they will see that Script to run is editor.html and here in our case it’s a vanity path, to it will result in calling “/libs/cq/gui/content/editor.html”(actual path of the Script).
3. From there the “sling:resourceType” is taking us to “cq/gui/components/authoring/editors/switch”, here the editing part of Touch UI would be catered.

Similarly for cf# its -> cq/ui/components/widget -> cq/ui/components/widget -> /libs/cq/ui/components/widget/html.jsp

Here’s one way to look for Resource resolution:

1. Head over to http://localhost:4502/system/console/servletresolver
2. Enter the request URL and select the appropriate HTTP method (http://localhost:4502/editor.html/content/we-retail.html)
3. The Opting servlets will be listed – I think the ‘chosen’ one is on the top…

Here’s another:

1. Head over to http://localhost:4502/system/console/requests and clear existing requests
2. ‘Edit’ a ‘simple’ AEM site (e.g. navigate to http://localhost:4502/editor.html/content/we-retail.html)
3. Refresh the page in #1 and locate your request
   1. It may happen that the page you are interesting in sends more than 20 requests – perhaps there’s a configuration to increase how many requests are ‘kept’ for analysis but I don’t know of it – instead, what you can try is to ‘cancel’ the page-load (so that further requests are not sent to the server)

The downside of 2^nd method is limited requests can be tracked this way – the upside is that you get a lot more information that the 1^st.

I hope this would help you.

Thanks and Regards

Kautuk Sahni