Are you able to edit the component in touch UI if you just drag and drop it to an empty parsys ? I tested the "data-sly-resource" in my component on 6.1 and I am able to edit in Touch UI. 

You can just add the following exclude rule for updating only the metadata - exclude    /content/dam/projectname/master/video(.*)/jcr:content/[ar].*

I think you need to register/install the custom node type named "tab_data_source" you might have created in 5.6 instance. 

From the exception stack trace it seems that you are trying to create a "cq:Dialog" type node(tab_data_source) under path "/apps/my-foundation/components/page/detail" which is of type "nt:folder". As per "nt:folder" node type definition in CRX you can not create direct child nodes of type "cq:Dialog...

That's because the type of page node is "nt:folder". Try changing the nodetype of page node and it should work.

You are missing primaryType property definition on the root node. Try the below XML and it should work- <?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" cq:actions="[text:myCalendar/_cq_editConfig:,edit,delete]" cq:dialo...

I followed the same steps on AEM 6.1 instance and it worked for me. I see Authentication Failed message only when I set wrong user name in the header value. Are you testing this on 6.0 version ? Do you see any exception/error in the logs ?  

You can use AEM RequestResponseFactory API to create the dummy request, response objects or else you can write custom classes which implement HttpServletRequest and HttpServletResponse interfaces.  http://docs.adobe.com/docs/en/cq/5-6-1/javadoc/com/day/cq/contentsync/handler/util/RequestResponseFact...

You can use https://sling.apache.org/apidocs/sling6/org/apache/sling/engine/SlingRequestProcessor.html. You can reference this service in your code and invoke the processRequest() method to get the final generated HTML response. You can create synthetic/mock request and response objects and pass the...

For 6.1, you should add AEM Uber Jar as dependency and remove the references to all individual API dependencies which are present in Uber Jar. <dependency> <groupId>com.adobe.aem</groupId> <artifactId>uber-jar</artifactId> <version>6.1.0</version> <classifier>obfuscated-apis</classifier> <scope>prov...