Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Enabling content as a service in AEM

Avatar

Avatar
Validate 10
MVP
kunal23
MVP

Likes

166 likes

Total Posts

565 posts

Correct Reply

172 solutions
Top badges earned
Validate 10
Validate 1
Ignite 3
Ignite 1
Give Back 50
View profile

Avatar
Validate 10
MVP
kunal23
MVP

Likes

166 likes

Total Posts

565 posts

Correct Reply

172 solutions
Top badges earned
Validate 10
Validate 1
Ignite 3
Ignite 1
Give Back 50
View profile
kunal23
MVP

06-08-2020

Content fragments can now be exposed via new AEM HTTP API.[0]

Is it okay to expose content fragments using this api to external applications or should we expose them via experience fragments, content fragments component and sling model exporter? Any recommendations ? With sling model exporter we have control on the JSON output but it requires additional steps from authors to set up experience fragments along with the content fragments.

 

[0] - https://docs.adobe.com/content/help/en/experience-manager-65/assets/extending/assets-api-content-fra...

View Entire Topic

Avatar

Avatar
Give Back 3
Level 4
SundeepKatepally
Level 4

Likes

76 likes

Total Posts

76 posts

Correct Reply

21 solutions
Top badges earned
Give Back 3
Boost 10
Boost 25
Boost 50
Affirm 10
View profile

Avatar
Give Back 3
Level 4
SundeepKatepally
Level 4

Likes

76 likes

Total Posts

76 posts

Correct Reply

21 solutions
Top badges earned
Give Back 3
Boost 10
Boost 25
Boost 50
Affirm 10
View profile
SundeepKatepally
Level 4

06-08-2020

Firstly:

Content Fragment - Is of type dam:asset having data without experience.

Experience Fragment - Is of type cq:Page , which will have data and experience.

 

Any Data stored is content fragment can be exposed as a content service using various ways

 

Option1: Write custom code , which will return the data to external application in json or xml format. 

  Pros: Full control on the contract. Any updates to the content fragment model like adding a new field etc will not impact the contract.

  Con : Developing a code example using servlet.

 

Option2 : Use the OOTB new AEM HTTP API

  Con: No control on the contract. Any new field additions will impact contract.

 

Option2: is suggestible for simple integrations.

Option1 : suggestible for complex integrations.

 

content fragment exposing vis experience fragment --> feel like invalid.