You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2013/05/07 18:41:16 UTC

[jira] [Created] (SLING-2860) Make ResourceCollectionManager an OSGi service

Carsten Ziegeler created SLING-2860:
---------------------------------------

             Summary: 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