[JCR-2042] RepositoryFactory implementation for jcr2spi

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.0-beta1
• Component/s: jackrabbit-jcr2spi, jackrabbit-spi
• Assignee: Michael Dürig
• Reporter: Marcel Reutegger
• Created: 25/Mar/09 13:40
• Updated: 11/Jan/10 14:18
• Resolved: 17/Sep/09 22:53

Description

There should be a RepositoryFactory implementation in jcr2spi that also covers acquiring the underlying RepositoryService.

For this purpose I suggest to create:

• a RepositoryServiceFactory in jackrabbit-spi, which encapsulates the spi implementation specifc instantiation of the RepositoryService. the factory probably just needs a single method that takes a parameters map.
• a RepositoryFactory implementation in jcr2spi, which works with a URI that contains all required information to connect/acquired the RepositoryService.

To use jcr2spi/spi2jcr/jackrabbit-core:

• jcr+file://path/to/repository/home?config=repository.xml

To use jcr2spi/spi2dav:

• jcr+dav://localhost:8080/server/repository/?br=4

To use jcr2spi/spi2davex:

• jcr+davex://localhost:8080/server/repository/

An implementation of RepositoryServiceFactory must check the scheme and decide if it can handle it and create a RepositoryService instance with it, otherwise it must return null. This means there would be a single name for the connect URI for all RepositoryServiceFactory implementations.

Issue Links

• blocks: JCR-2309 Remove excessive dependencies from jcr-client module