You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Eric Norman (Jira)" <ji...@apache.org> on 2020/09/09 18:16:00 UTC
[jira] [Resolved] (SLING-9719) Utilize any available oak
EditorProvider components that were declared
[ https://issues.apache.org/jira/browse/SLING-9719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Norman resolved SLING-9719.
--------------------------------
Resolution: Fixed
Fixed at: https://github.com/apache/sling-org-apache-sling-jcr-oak-server/commit/77c571f03362f1d7b4ec33842c09ef23c85759ed
> Utilize any available oak EditorProvider components that were declared
> ----------------------------------------------------------------------
>
> Key: SLING-9719
> URL: https://issues.apache.org/jira/browse/SLING-9719
> Project: Sling
> Issue Type: Improvement
> Reporter: Eric Norman
> Assignee: Eric Norman
> Priority: Major
> Fix For: JCR Oak Server 1.2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{OakSlingRepositoryManager}} is not utilizing the {{EditorProvider}} components provided by bundles.
> To better align with the oak-jcr RepositoryManager implementation, the sling impl should also utilize the WhiteboardEditorProvider to listen for and utilize any registered EditorProvider components that are available.
> This change will automatically enable support for {{mix:atomicCounter}} via the {{AtomicCounterEditorProvider}} that's not used at the moment.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)