Thanks, Sent you a message. Not sure if I am eligible but sent you the info.

@Mayank_Gandhi - Updated my comment

I am getting redirected to https://downloads.experiencecloud.adobe.com/content/software-distribution/en/pswelcome.html?packagePath=/content/companies/public/adobe/packages/cq650/servicepack/fd/AEM-Forms-6.5.3.0-WIN.Onclick of 'Got it' I am redirected to Earlier I used to have access to package share...

Can you try something like this below?@Model(adaptables = { Resource.class, SlingHttpServletRequest.class }) public class Test { @ScriptVariable private Page currentPage; @PostConstruct public void init() { Resource currentPageRes = currentPage.adaptTo(Resource.class); Resource currentPageContentR...

Did you try the comment at https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/get-component-resource-in-a-servlet/qaq-p/387895 ? Seems like we are getting the node from the component i.e under /apps so try to see if the option of getting the page resource works or using a admi...

How is the call to servlet made? If there is an Ajax call via js, may be pass the resource path as a query param or form data making it a post call. That way we can doString path = request.getParameter("resourcePath").String path = request.getParameter("resourcePath"); Resource resource = request.ge...

What is the value of (String)request.getAttribute(Value.CONTENTPATH_ATTRIBUTE) when you debug? We can check if its a valid resource path. May be if it has selector or something, we can try resolver.resolve(pathobtained)Also check if the resolver has correct access, may be we need to use a admin user...

Few thoughts - Start with basic web development languages html, css, js, jquery and Java. More items to look into - Java content repositories, OSGi, SLING and AJAXAlso see - https://experienceleague.adobe.com/docs/experience-manager-64/developing/home.html?lang=en#devtools Try hands on component dev...

Noticed same that use of selector gives a 404. Can you see if using a query parameter ?v=123456 (/content/dam/static/fonts/icon-font/icon-font.1234.ttf and /content/dam/static/fonts/icon-font/icon-font.ttf.transform/original/icon-font.ttf?v=1605545369) works for you? Might need to check any node js ...

It seems like this could be a use case for Content Fragments https://helpx.adobe.com/experience-manager/using/content-fragments.html in case where there are multiple partners sharing/using same content. By using CF the source remains same and the content can be used for different views for the desir...