[ https://issues.apache.org/jira/browse/SLING-8309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Lietz resolved SLING-8309. --------------------------------- Resolution: Won't Fix > Allow adding CommitHooks and EditorProviders dynamically from bundles > --------------------------------------------------------------------- > > Key: SLING-8309 > URL: https://issues.apache.org/jira/browse/SLING-8309 > Project: Sling > Issue Type: Improvement > Components: Oak > Reporter: Sergiu Dumitriu > Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > Currently, {{OakSlingRepositoryManager}} uses a hard-coded list of > {{CommitHook}} and {{EditorProvider}} to be used by the Oak repository. This > means that other than building a patched version of > {{OakSlingRepositoryManager}} there's no way to include a new commit > observer. Ideally, a single pseudo-\{{CommitHook}} and > pseudo-\{{EditorProvider}} should be handled to Oak, and these should just > dynamically aggregate all theĀ {{CommitHook}} andĀ {{EditorProvider}} instances > registered in the {{Whiteboard}}. > All the currently hardcoded components are already available in the > whiteboard, so no functionality will be lost, but this change will > automatically enable support for {{mix:atomicCounter}} via the > {{AtomicCounterEditorProvider}} that's not used at the moment. > The old behavior should still be available via a new configuration, > {{OakSlingRepositoryManagerConfiguration#dynamic_components}}. -- This message was sent by Atlassian Jira (v8.20.7#820007)