[
https://issues.apache.org/jira/browse/SLING-8309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791738#comment-16791738
]
angela commented on SLING-8309:
-------------------------------
[~sdumitriu], [~edn], i share [~mduerig] concern regarding {{CommitHook}}s and
{{CommitEditor}}s. However, what seems to be at the bottom of this issues is
the wish to plug a custom {{Observer}}. Please note, that this is already
possible today with the existing Sling setup and you don't have to change the
set of hooks/editors. As a matter of fact I actually implemented a custom
{{Observer}} myself in AEM and it worked like a charm without having to touch
the repository setup. As far as I remember [~teofili] did the same for an
custom extension of the Sling Distribution (aka Replication). So, there is for
sure knowledge present within the Sling community on how to plug a custom Oak
{{Observer}} at runtime.
Hope that helps
> 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: 0.5h
> 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
(v7.6.3#76005)
