check the OOB image component in the foundation /libs/foundation/components/image/dialog/items/imagetry using the same item in your component aswell and see if it worksshare your dialog so see if anything is missing

I agree with @scott, you dont need to do resource.getResourceType for herotext2. Example which he mentioned should help

actually all the rules are executed in the order its been creaeted

According to your code snapshot,'resource' contains the current resource which is datasource and thats the expected behavior !check the below thread which may be of a helphttp://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__vund-hi_i...

Yes, it does in the orderIn your order, last rule '/0003' is deny everything with /ajax/ and hence it is not caching. Change the /type "allow" and it should be caching the same.

Krishh,You can also refer [1] for more details and options[1] http://adobeaemclub.com/root-mapping-configuration-in-adobe-aem/

Hi Praveen,Check [1] . I have detailed out multiple ways of doing the same  [1] http://adobeaemclub.com/root-mapping-configuration-in-adobe-aem/

doc mentioned by @scott would give you the details of how to configure. If you are looking for any specific usecase, let us know.

Krishh,for node '/content' there are 2 propertiessling:resourceType as sling:redirect andsling:target as /geohomechange '/geohome' to the path for your application and replicate the same to publish instance. This should solve your problem. Regards,bsloki

Using repository.xml, we could have set up active/active or active/passive shared data stores in the previous versions where as from 6.x, OAK doesnt support the same and hence for publish clustering we need to go with mongo DB and for author only cold stand by is supported. You really cant have acti...