Thursday, 5 June 2014

Interact with CQ/AEM


Location of CQ5 elements

1 OSGi Bundles

2 Templates
3 components - page, contents [JSP Scripts or Servlets are used to render components in CQ.]
4 Static files

global.jsp
------------
What is the use of including Global.JSP <%@include file="/libs/foundation/global.jsp"%> ? Why global.JSP file is getting included default when you create a new component?


  • global.jsp file is having many useful implicit objects available once included.
  • it supports usage of cq taglibs
Read More: 
Solr and AEM
JSON for Solr
AEM INTERNALIZATION
Search Persistance
Navigation in AEM
Website design steps in AEM

API's to interact with CQ/AEM Apps
-------------
1 CQ or WCM API
2 Sling API
3 JCR API


Side kick-

How the sidekick appear/disappear in a page?
----------
WCM initialization code calls the side kick. So it appears
location of side kick code: /libs/wcm/core/components/init/init.jsp

Just include below code in your JSP. It brings side kick
<cq:include script="/libs/wcm/core/components/init/init.jsp" />

Include option for JSP
------------------------
Compile time - <%@include file="/libs/foundation/global.jsp" %>
run time - <cq:include script="/libs/foundation/global.jsp" %>
run time - <sling:include resource="<%=par%>" %>


Options available to access content in CQ5 WCM/AEM


=============WCM API [currentPage object ]================<br>

<%=currentPage.getTitle()%> <br>

=============Sling API[properties object ]================<br>

<%=properties.get("jcr:title")%> <br>

=============JCR API[currentNode object ]==================<br>


<%=currentNode.getProperty("jcr:title").getString()%>

No comments:

Post a comment