AEM 6.3 : Is it possible to extend Content Fragments content delivery implementation?

Avatar

Avatar

Sagar_Sane

Avatar

Sagar_Sane

Sagar_Sane

05-02-2018

Hello all,

I saw that in AEM 6.3, there is already built in orchestration to manage dispatcher flush, etc. of referenced Content Fragments on AEM pages.

Documentation here: Adobe Experience Manager Help | Understanding AEM Content Fragment Delivery Considerations

I was curious whether its possible to extend this orchestration which is done using Sling Jobs for any custom reference components on the site? For example, if I have a custom reference component (which is not based on the foundation reference component), will I be able to use the implementation built for Content Fragments?

Thank you,

Sagar Sane

Replies

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K
smacdonald2008

12-02-2018

This is an AEM feature - not a component that can be overlayed or modified.

Avatar

Avatar

Sagar_Sane

Avatar

Sagar_Sane

Sagar_Sane

12-02-2018

Thank you Scott.

Yes I understand. Though I was curious whether the feature was customizable to allow for providing a custom resourceType to the Sling Job topic.

I think it is a very useful feature so I was hoping to reuse it for a custom resourceType (especially to reuse the dispatcherflush module).

Thanks,

Sagar