I would suggest to configure the URLs in run mode specific OSGI configuration nodes. And then you can read those variables in the page head.jsp and render them as global variables inside the <script> tag.  The JS file can simply use these variables to fetch the URLs value. 

I found that the commerce.api package is exported by the cq-commerce-core bundle in 6.2. There is no separate bundle which exports the commerce API. Therefore, you can try with the following dependency in your project- <dependency> <groupId>com.adobe.cq.commerce</groupId> <artifactId>cq-commerce-cor...

I do not think there is anything to do with Uber Jar as you are able to compile your code. The exception you see is a run time exception when you execute your workflow process. Check in the Apache felix console whether the process step component class is in active state or not. If you do not see the...

Why you want to list all the servlets running in AEM ? There are too many servlets which have nothing to do with forms. If you want to list all the custom servlets registered for the forms then you can use OSGI APIs to dynamically find all the servlets and then extract their URL property. Example - ...

Try either of the following-title.setAttribute("style","display:none") OR $form.find("[name='./jcr:Heading']").hide()

I don't have access to CQ 5.4 instance so I can not check it my self but I am sure there should be some OSGI configuration for enabling the audit logger as pointed by the below pages. http://stackoverflow.com/questions/34398028/node-folder-deletion-history-adobe-aem-cqhttp://cq-ops.tumblr.com/post/3...

Thanks for the detailed explanation. I didn't know that you were using sightly to include the components. Please refer the following thread which has solution to this problem - http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__7wh...

Apologies for the wrong code snippet. You can follow this KB article for the correct API - https://helpx.adobe.com/experience-manager/kb/ComponentDiv.html.  This should fix the problem-<%@ page session="false" import="com.day.cq.wcm.api.WCMMode, com.day.cq.wcm.api.components.IncludeOptions" %> if (W...

You can remove this divs by adding the following lines of code in global.jsp file- (WCMMode.fromRequest(request) != WCMMode.EDIT && WCMMode.fromRequest(request) != WCMMode.DESIGN) { IncludeOptions.getOptions(request, true).forceSameContext(Boolean.TRUE); }

Refer the solution in the following thread- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__7whj-i_am_using_sightlyf.html