[SLING-2860] Make ResourceCollectionManager an OSGi service

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Resource Collections 1.0.0
• Assignee: Carsten Ziegeler
• Reporter: Carsten Ziegeler
• Created: 07/May/13 16:40
• Updated: 08/Mar/14 16:20
• Resolved: 07/May/13 17:23

Description

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