Tuesday, April 2, 2019

Exception while browsing the tags in page creation wizard: The method transform(Object) of type new Transformer(){} must override a superclass method - AEM

Exception while browsing the tags in page creation: The method transform(Object) of type new Transformer(){} must override a superclass method - AEM 

We were getting the following exception while browsing the tags in page creation wizard - http://localhost:4502/mnt/overlay/cq/gui/content/coral/common/form/tagfield/picker.html?root=%2fetc%2ftags&selectionCount=multiple&_=1554223439347 500 (Server Error)




The below exception is displayed while trying to open the above mentioned URL

Compilation errors in /libs/cq/gui/components/coral/common/form/tagfield/datasources/children/children.java: Line 78, column 3367 : The method transform(Object) of type new Transformer(){} must override a superclass method
Cannot serve request to /mnt/overlay/cq/gui/content/coral/common/form/tagfield/picker.html in /libs/cq/gui/components/coral/common/form/tagfield/datasources/children/children.java

org.apache.sling.scripting.java.impl.ServletWrapper$CompilerException: Compilation errors in /libs/cq/gui/components/coral/common/form/tagfield/datasources/children/children.java:
Line 78, column 3367 : The method transform(Object) of type new Transformer(){} must override a superclass method


Steps to resolve the issues:

Clear the compiled JSP cache:

The compiled jsp class files might have corrupted, follow the below steps to remove the existing classes and recompile the JSP's

Go to http://aem-host:port/system/console/slingjsp
Click Recompile all JSPs.

Unfortunately the specified issue was not resolved after clearing the cache.

Verify the Source VM and Target VM in Apache Sling Java Script Handler:

Ensure the the Source VM and Target VM values are specified with the version the AEM server is running or specify as auto to automatically consider the current VM version.

In our case the VM version was pointing to 1.5 but our current VM version is 1.8, the issue was resolved after changing the VM versions to auto.

This issue was observed in AEM 6.4 version after upgrading from AEM 6.2, the same VM version(1.5) was working in AEM 6.2 without any issue.



Wednesday, March 6, 2019

How to get the currentPage URL in cq:dialog dropdown datasources?

How to get the currentPage URL in cq:dialog dropdown datasources?

In Touch UI dialog's, the dynamic dropdownlist are loaded through data sources, sometime we may need to get the current page URL from where the dialog is opened to load the dropdownlist data.

String path= request.getParameter("item");

Returns the content path with out jcr:content, e.g /content/test/en/home

String path = (String) request.getAttribute(com.adobe.granite.ui.components.Value.CONTENTPATH_ATTRIBUTE);

Returns the path with jcr:content, e.g /content/test/en/home/jcr:content

import java.io.IOException;
import java.util.ArrayList;
import java.util.HashMap;
import java.util.Map;
import java.util.LinkedHashMap;

import javax.servlet.Servlet;
import javax.servlet.ServletException;

import org.apache.sling.api.SlingHttpServletRequest;
import org.apache.sling.api.SlingHttpServletResponse;
import org.apache.sling.api.resource.Resource;
import org.apache.sling.api.resource.ResourceResolver;
import org.apache.sling.api.resource.ResourceResolverFactory;
import org.apache.sling.api.resource.ValueMap;
import org.apache.sling.api.servlets.SlingSafeMethodsServlet;
import org.apache.felix.scr.annotations.Reference;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.apache.felix.scr.annotations.Service;
import org.apache.felix.scr.annotations.Component;
import org.apache.felix.scr.annotations.Properties;
import org.apache.felix.scr.annotations.Property;

import org.apache.sling.api.wrappers.ValueMapDecorator;
import com.adobe.granite.ui.components.ds.DataSource;
import com.adobe.granite.ui.components.ds.SimpleDataSource;
import com.adobe.granite.ui.components.ds.ValueMapResource;

import com.adobe.granite.ui.components.Value;
import org.apache.sling.api.resource.ResourceMetadata;;

@Service(value = Servlet.class)
@Component(metatype = true)
@Property(name = "sling.servlet.resourceTypes", value = "/services/availableCountryDataSource1"),
@Property(name = "service.description", value = "Get country list"),
@Property(name = "label", value = "countryList") })

public class AvailableCountryDataSource extends SlingSafeMethodsServlet {

private ResourceResolverFactory resolverFactory;

private static final long serialVersionUID = 1180258251365536303L;

private static final Logger log = LoggerFactory.getLogger(AvailableCountryDataSource.class);
protected void doGet(SlingHttpServletRequest request,SlingHttpServletResponse response) throws ServletException,IOException {

final Map<String, String> countriesdata = new LinkedHashMap<String, String>();
Map<String, Object> param = new HashMap<String, Object>();
    param.put(ResourceResolverFactory.SUBSERVICE, "Albin");
    ResourceResolver resourceResolver=null;

ArrayList<Resource> countryList = new ArrayList<Resource>();
ValueMap valueMap = new ValueMapDecorator(new HashMap<String, Object>());
ValueMap properties =null;

String resourcePath =(String)request.getAttribute(Value.CONTENTPATH_ATTRIBUTE);
resourceResolver = resolverFactory.getServiceResourceResolver(param);
Resource resource = resourceResolver.getResource(resourcePath);

String data = properties.get("countryList", (String) null);

    if(data != null ){
log.error("INSIDE IF");
ValueMap vm =null;
for(String country : data.split(",")){

String[] tokens = country.split(";");
if(tokens == null || tokens.length != 2){
vm = new ValueMapDecorator(new HashMap<String, Object>());
vm.put("value", tokens[0] );
vm.put("text",  tokens[1]);

countryList.add(new ValueMapResource(request.getResourceResolver(),new ResourceMetadata(), "nt:unstructured", vm));

DataSource dataSource = new SimpleDataSource(countryList.iterator());
request.setAttribute(DataSource.class.getName(), dataSource);

}catch(Exception e){
log.error("Error while retrieving countries.",e);


Wednesday, February 27, 2019

Adobe Experience Manager(AEM) 6.4 - Touch UI conversion Tips

Adobe Experience Manager(AEM) 6.4 - Touch UI conversion Tips

This post explains some of the issues identified during Touch UI conversion in AEM 6.4.

Embedded child components are not editable in Touch UI:

The Touch UI editing is not enabled for the components embedded in another component


The component2 is embedded in component 1(component1.html)

 <div data-sly-resource ="${ @path='component2', resourceType='/apps/test/components/component2 '}" >

The edit option is enabled for parent component(componet1) but not for child component(component2)


The embedded component editing is not enabled if the parent component also included the parsys through sly tag.

The issue is resolved after replacing the sly tag with div tag

<sly  data-sly-resource ="${ @path='cartBottomParsys', resourceType='wcm/foundation/components/parsys'}"/>


<div data-sly-resource ="${ @path='cartBottomParsys', resourceType='wcm/foundation/components/parsys'}"/>


cq:dialog Inheritence:

Parent dialog tabs and properties are displayed(Inherited) in the child component  in Touch UI but the same is not inherited in classic UI.

To hide the parent dialog tabs and properties in child components add the below property to the items node under tabs node in child component - e.g /apps/test/components/pages/homepage/cq:dialog/content/items

Name: sling:hideChildren
Type: String[]
Value: *

To hide the specific tabs from parent component

Name: sling:hideChildren
Type: String[]
Value: tab1,tab2


Hide/show tabs in Coral 3 UI dialog

Adobe Experiance Manager(AEM) 6.4 - Upgrade Tips

This post explains some of the issues identified during AEM 6.4 upgrade.

The Servlet status is disabled in AEM

/etc/cloudsettings/default/contexthub.kernel.js is not loading

Proxy ClientLibs not working through Dispatcher

Touch UI dialog is not enabled:

The touch UI dialog's were not enabled for non of the components after applying 6.4.3 on top of 6.4.2

This is a known issue in AEM 6.4.3, the following workaround can be followed to fix the issue

 Go to Package Manager
 Reinstall package ""cq-ui-wcm-admin-content-1.0.1004.zip""
 Recompile all JSPs (http://<AEM HOST>:<AEM PORT/system/console/slingjsp)

Refer the following Adobe document for more details - https://helpx.adobe.com/experience-manager/6-4/release-notes/sp-release-notes.html

Tuesday, February 12, 2019

The Servlet status is disabled in AEM(Adobe Experience Manager) 6.4

The Servlet status is disabled in AEM(Adobe Experience Manager) 6.4

The Servlet created with Archetype 10 is disabled while deploying the same to AEM 6.4(the same is applicable for the Servlet developed in AEM 6.4 with OSGI annotation)




The servlet code(enabled with scr annotation)

package config.core.servlets;

import java.io.IOException;
import java.util.*;
import javax.servlet.*;

import org.apache.sling.api.*;
import org.apache.sling.api.resource.ResourceResolver;
import org.apache.sling.api.servlets.*;
import org.osgi.framework.Constants;
import org.apache.sling.commons.json.*;

import org.apache.felix.scr.annotations.*;
import org.apache.felix.scr.annotations.sling.SlingServlet;
import org.apache.felix.scr.annotations.ConfigurationPolicy;

@Component(policy = ConfigurationPolicy.REQUIRE)
@SlingServlet(paths = "/bin/servlet/selector1", selectors = "dynamicpopulate",
    extensions = "json", methods = "GET", generateComponent = false, generateService = false)

public class FirstServletSelector1 extends SlingAllMethodsServlet {

    protected void doGet(SlingHttpServletRequest request, SlingHttpServletResponse response)
    throws ServletException, IOException {
        JSONArray jsonArray = new JSONArray();
        JSONObject jsonObject = new JSONObject();
        JSONObject jsonObject1 = new JSONObject();
        JSONObject jsonObject2 = new JSONObject();

        try {

            jsonObject.put("value", "1");
            jsonObject.put("text", "Albin1");
            jsonObject1.put("value", "2");
            jsonObject1.put("text", "Albin2");
        } catch (JSONException e) {
            // TODO Auto-generated catch block



The issue is ConfigurationPolicy is defined as REQUIRE but there is no sling:OsgiConfig defined in the repository for the servlet PID.

When we make component 'policy' to 'REQUIRE', OSGi container expects corresponding configuration object (osgi:Config node) to become satisfied

The issue can be resolved either one of the below approach
  • Change the ConfigurationPolicy.REQUIRE to ConfigurationPolicy.OPTIONAL in case the sling:OsgiConfig is not mandatory to enable this servlet
  • Enable the sling:OsgiConfig in the repository with required configuration values for this servlet

The servlet is in Active state after following one of the above approach.

The details mentioned in this post is one of the reason to mark the Servlet status as disabled.