Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Invalid recursion selector value 'model'

Avatar

Level 4

Hi All,

I have created a content fragment using a content fragment model. I have added that fragment onto one sample page using content fragment component and I can see the content on the page.

But whenever I am trying to access the content services for that particular page or content fragment, I am getting below error :

I am accessing page as : http://<serverip:4502/<contentpath>/123.model.json

Invalid recursion selector value 'model'

Cannot serve request to /<contentPath>/123.model.json in org.apache.sling.servlets.get.DefaultGetServlet

I am not sure if I am missing any configuration here or it is something wrong in my sling mapping.

Thanks

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

I still have doubt, because json can't expose binary data.

And CF content stored as binary.



Arun Patidar

View solution in original post

8 Replies

Avatar

Community Advisor

Hi,

What AEM version are you using?



Arun Patidar

Avatar

Level 4

Hi Gaurav

Thank you for the reply.

But here I am not even getting JSON response for page and github link provided in the solution is also not working.

Please let me know if you have any alternate solution.

Avatar

Community Advisor

I believe the model exporter functionality is implemented only for cq:Page type, but not for assets.

When you use model selector the binary data is replaced with size in json, JSON response doesn't show binary data in response.

Since CF stores data as assets(binary) and model selector doesn't return binary, so if implementing model selector for CF make no sense.



Arun Patidar

Avatar

Correct answer by
Community Advisor

I still have doubt, because json can't expose binary data.

And CF content stored as binary.



Arun Patidar

Avatar

Level 1

make sure your page resouceSuperType is referencing core/wcm/components/page/v1/page or core/wcm/components/page/v2/page