sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <>
Subject [jira] [Commented] (SLING-8309) Allow adding CommitHooks and EditorProviders dynamically from bundles
Date Wed, 13 Mar 2019 13:41:00 GMT


Michael Dürig commented on SLING-8309:

I would strongly advice against exposing commit hooks at the OSGi level. You are drilling
a whole right into the most sensible core of your content repository putting data consistency
and security at risk. 

cc [~mreutegg] [~tmueller] [~frm] [~anchela]

> Allow adding CommitHooks and EditorProviders dynamically from bundles
> ---------------------------------------------------------------------
>                 Key: SLING-8309
>                 URL:
>             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

View raw message