Invalid recursion selector value 'caas' in AEM 6.5 | Community
Skip to main content
sareshpp9060331
sareshpp9060331
New Participant
July 21, 2020
Solved

Invalid recursion selector value 'caas' in AEM 6.5

  • July 21, 2020
  • 3 replies
  • 2009 views

In AEM 6.3, we could expose our page content as JSON without using Content Fragments or Experience Fragments with the extension caas.json (e.g. localhost:4502/content/we-retail/us/en/men.caas.json) to 3rd party apps.

 

AEM 6.3 output : 

 

After migrating to AEM 6.5, when we hit the same URL, we receive an error saying - Invalid recursion selector value 'caas'

 

AEM 6.5 error

 

In the release notes of AEM 6.5 we did not find any deprecation/removal of this feature.

Any idea as to why it's not working?



 

 

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

Starting from 6.4, its exposed via .model.json. Like http://localhost:6481/content/we-retail/us/en.model.json.

3 replies

Ankur_Khare
Ankur_Khare
New Participant
July 23, 2020

I haven't used in aem 6.3 but it seems this "caas" selector is not working on aem 6.5.

And to consume it as content as a service you should be following this-

 

https://docs.adobe.com/content/help/en/experience-manager-64/developing/components/json-exporter.html

    Shashi_Mulugu
    Shashi_Mulugu
    New Participant
    July 23, 2020

    Please refer to this community post:-

     

    https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-content-services-caas-aem-6-5/qaq-p/315846

      vanegi
      vanegiAccepted solution
      Employee
      July 21, 2020

      Starting from 6.4, its exposed via .model.json. Like http://localhost:6481/content/we-retail/us/en.model.json.

        sareshpp9060331
        sareshpp9060331Author
        New Participant
        July 21, 2020

        Hi @vanegi,
        In 6.3, with caas.json the output was refined and there was no junk data like responsivegrid, gridClassNames, etc unlike using model.json in 6.5. 

        Also, page properties value were available using caas.json which is not the case with model.json in 6.5

        Since we have used the output of caas.json for our 3rd party applications, is there a way we can get almost similar like experience in AEM 6.5 as well with model.json or any other way without creating CF or XF?

        Terms & ConditionsAccessibility statement

        Loading footer...