Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Include ExperienceFragmentsAdapaterFactory by default in aemContext

Description

When using ExperienceFragments, adapting from a Page to an ExperienceFragment or ExperienceFragmentVariation will return null by default. A workaround for this is to register the AdapterFactory manually:

It would be an improvement to have these Services/Factories registered by default.

Activity

Show:

Stefan Seifert July 30, 2018 at 1:40 PM

the classes ExperienceFragmentsServiceFactoryImpl and ExperienceFragmentsAdapaterFactory your mention are not part of the public AEM API and are not exported by the bundle com.adobe.cq.cq-experience-fragments.

can you come up with a PR with a suitable mock implementation of the adapter factory and the related interfaces ExperienceFragment, ExperienceFragmentVariation, and - if required - ExperienceFragmentsServiceFactory, ExperienceFragmentsService.

Stefan Seifert June 27, 2018 at 2:20 PM

thanks for the proposal - i'll have a look at it.

Details

Assignee

Reporter

Components

Affects versions

Priority

Created June 25, 2018 at 3:13 PM
Updated July 30, 2018 at 1:40 PM
Configure