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
  • 7793 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

      Vijayalakshmi_S
      Vijayalakshmi_S
      Level 10
      November 18, 2021

      Actually, we are planning to use the exporter at two level, one is page level and second is component level, but we want to run these exporter on the basis of selector.

       

       

      contentservices/components/structure/page - It's resource super type is core/wcm/components/page/v2/page 

       

      Please let me know if you need any further details.

       

      Thanks

       


      Thanks for the inputs @vikrams57194913 

      Can you share the complete Java package name of PageExporter that you are implementing from. 

       

        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...