SlingRepository#loginAdmin shouldn't be used at all. ResourceResolverFactory is the service to be used.
I think we had a discussion some time back about undeprecating RRF#loginAdmin and we decided against it. So I think the same arguments (whatever they were) hold true for SR#loginAdmin. loginAdmin should not be used by average code and it seems deprecation is the only vehicle we have that works Regards Carsten Robert Munteanu wrote > Hi, > > Following dev@sling discussions [1] and Jira issue [2] I've filed a PR > to un-deprecate loginAdministrative [3]. > > Comments/reviews are most welcome, I plan to merge this next Monday. > > Thanks, > > Robert > > [1]: https://issues.apache.org/jira/browse/SLING-7613 > [2]: > http://apache-sling.73963.n3.nabble.com/Deprecation-of-SlingRepository-loginAdministrative-td4081024.html > [3]: https://github.com/apache/sling-org-apache-sling-jcr-api/pull/1 > -- Carsten Ziegeler Adobe Research Switzerland [email protected]
