Sling Model with custom selector not working in AEM 6.5 | Community
Skip to main content
V
vikrams57194913
Level 2
November 18, 2021

Sling Model with custom selector not working in AEM 6.5

  • November 18, 2021
  • 2 replies
  • 7779 views

Hi All,

 

I am using a Sling model exporter to export json data in AEM 6.5 and using the selector "caas". When the selector is "model" , it works perfectly. However with custom selector , it shows the below error.

 

Invalid recursion selector value 'caas'

Cannot serve request to /content/abc/internal/exportsite/en/clientaccess/help/secondlevela/level3.caas.json in org.apache.sling.servlets.get.DefaultGetServlet

 

Already tried the below:

check if this helps - Re: Sling Exporter with custom selector

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Asutosh_Jena_
Community Advisor
Asutosh_Jena_Community Advisor
Community Advisor
November 18, 2021

Hi @vikrams57194913 

 

Is /content/abc/internal/exportsite/en/clientaccess/help/secondlevela/level3 a page?

Did you try with /content/abc/internal/exportsite/en/clientaccess/help/secondlevela/level3/jcr:content.caas.json?

 

Thanks!

    V
    vikrams57194913Author
    Level 2
    November 18, 2021

    I am getting blank page with the above link also, only getting response from model.json

     

    Thanks

      V
      vikrams57194913Author
      Level 2
      November 19, 2021

      Please share your model class - PageExporterImpl (that introduced this exception)


      package ca.sunlife.web.contentservices.core.impl;

      import com.adobe.cq.export.json.ComponentExporter;
      import com.adobe.cq.export.json.ExporterConstants;
      import com.day.cq.wcm.api.NameConstants;
      import com.day.cq.wcm.api.Page;
      import lombok.experimental.Delegate;
      import org.apache.sling.api.SlingHttpServletRequest;
      import org.apache.sling.api.resource.ValueMap;
      import org.apache.sling.models.annotations.DefaultInjectionStrategy;
      import org.apache.sling.models.annotations.Exporter;
      import org.apache.sling.models.annotations.Model;
      import org.apache.sling.models.annotations.Via;
      import org.apache.sling.models.annotations.injectorspecific.ScriptVariable;
      import org.apache.sling.models.annotations.injectorspecific.Self;
      import org.apache.sling.models.annotations.via.ResourceSuperType;

      import javax.annotation.PostConstruct;
      import javax.inject.Inject;

      import java.util.Calendar;
      import java.util.Locale;
      import java.util.Map;

      @Model(adaptables = SlingHttpServletRequest.class,defaultInjectionStrategy = DefaultInjectionStrategy.OPTIONAL, adapters = {com.adobe.cq.wcm.core.components.models.Page.class}, resourceType = PageExporterImpl.RESOURCE_TYPE)
      @3484101(name = ExporterConstants.SLING_MODEL_EXPORTER_NAME, selector = "mobile", extensions = ExporterConstants.SLING_MODEL_EXTENSION)
      public class PageExporterImpl implements com.adobe.cq.wcm.core.components.models.Page {

      protected static final String RESOURCE_TYPE = "contentservices/components/structure/page";

       

      @Delegate(types = com.adobe.cq.wcm.core.components.models.Page.class, excludes = Handled.class)
      @1961677
      @2434638(type = ResourceSuperType.class)
      private com.adobe.cq.wcm.core.components.models.Page pageDelegate;

      @9944223
      public Map<String, ? extends ComponentExporter> getExportedItems() {
      return pageDelegate.getExportedItems();
      }

      public String getMessage() {
      return "Custom Page Exporter Impl";
      }

      protected static interface Handled {
      public Map<String, ? extends ComponentExporter> getExportedItems();
      }

      }

        V
        vugaraghayev
        September 21, 2022

        Hi Vikram, 

        Add the caas.json.jsp file in the project and update its content as below: 

         

        /apps/cq/Page/caas.json.jsp 

        <%@include file="/libs/cq/Page/proxy.jsp" %>

         

        Update the workspace filter so changes are picked up: 

        <filter root="/apps/cq/Page">

         

        This should work. You can add multiple selectors with this way. 

         

        Another solution is to combine your custom selector with the OOTB model selector e.g model.caas

          Terms & ConditionsAccessibility statement

          Loading footer...