[
https://issues.apache.org/jira/browse/SLING-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2860.
-------------------------------------
Resolution: Fixed
I've changed the manager to be an OSGi service, updated the javadocs
> Make ResourceCollectionManager an OSGi service
> ----------------------------------------------
>
> Key: SLING-2860
> URL: https://issues.apache.org/jira/browse/SLING-2860
> Project: Sling
> Issue Type: Improvement
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Resource Collections 1.0.0
>
>
> As discussed on the mailing list, the ResourceCollectionManager should be a
> plain OSGi service. As each method takes a Resource as an argument, each
> method gets indirectly a resource resolver, so there is no need for the
> manager to keep a reference to the resource resolver.
> For convenience, supporting the adapter pattern resource resolver -> resource
> collection manager makes sense.
> The only method we have to remove is the getResourceResolver() method from
> the manager
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
