You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2025/03/13 14:17:00 UTC

[jira] (OAK-11601) Provide a better alternative for the deprecated RootProvider, or un-deprecate

    [ https://issues.apache.org/jira/browse/OAK-11601 ]


    Julian Reschke deleted comment on OAK-11601:
    --------------------------------------

was (Author: reschke):
My 2 cents: if something is deprecated, we need to point out what to do instead, even if this means pointing to OSGi.

> Provide a better alternative for the deprecated RootProvider, or un-deprecate
> -----------------------------------------------------------------------------
>
>                 Key: OAK-11601
>                 URL: https://issues.apache.org/jira/browse/OAK-11601
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>            Reporter: Thomas Mueller
>            Assignee: Angela Schreiber
>            Priority: Major
>
> oak-core:
> {noformat}
> package org.apache.jackrabbit.oak.plugins.tree.factories;
> /**
>  * Factory to obtain immutable {@code Root} objects.
>  *
>  * @deprecated Please use {@code RootProvider} instead
>  */
> public final class RootFactory {
> {noformat}
> But RootProvider is an interface, and the only(?) implementation (RootProviderService) just calls this class as well. And we would have to first create a new instance.
> This was deprecated in OAK-7015 but I don't see why exactly, and what would be the real replacement.
> TreeFactory seems similar.
> Both RootFactory and TreeFactory are widely used. It seems before we deprecate things, we should have a good replacement. Replacements that just call the deprecated method don't seem useful.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)