[jira] [Closed] (SLING-5513) Deprecate JcrResourceUtil

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-5513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-5513.
-----------------------------------

> Deprecate JcrResourceUtil
> -------------------------
>
>                 Key: SLING-5513
>                 URL: https://issues.apache.org/jira/browse/SLING-5513
>             Project: Sling
>          Issue Type: Task
>          Components: JCR
>    Affects Versions: JCR Resource 2.7.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: JCR Resource 2.7.2
>
>
> I think we should deprecate the jcr resource API completely, most of it
> is already deprecated. Deprecating will allow us to get rid of it in the
> future and reduce the parts we have to maintain.
> Most of that API is very old and was created in a time where we didn't
> have CRUD support for resources. Now that we have this for some time,
> there shouldn't be a need for any of this API. And if so, jackrabbit
> would be a much better place.
> Right now, we still have not deprecated:
> JcrResourceUtil#query - Resource Resolver should be used instead.
> JcrResourceUtil#toJavaObject - Value Map should be used instead.
> JcrResourceUtil#createValue - Modifiable Value Map should be used instead.
> JcrResourceUtil#setProperty - Modifiable Value Map should be used instead.
> JcrResourceUtil#createPath - ResourceUtil#getOrCreateResource should be
> used instead
> This leaves us with some constants in JcrResourceConstants. Although I
> would love to get rid of them to not have any API at all in the jcr
> resource bundle, some of them are really related to the jcr resource
> provider.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)