You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2009/09/16 14:20:57 UTC

[jira] Updated: (JCR-2042) RepositoryFactory implementation for jcr2spi

     [ https://issues.apache.org/jira/browse/JCR-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dürig updated JCR-2042:
-------------------------------

    Attachment: JCR-2042-poc.patch

Here's the patch mentioned in my previous comment

> RepositoryFactory implementation for jcr2spi
> --------------------------------------------
>
>                 Key: JCR-2042
>                 URL: https://issues.apache.org/jira/browse/JCR-2042
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: jackrabbit-jcr2spi, jackrabbit-spi
>    Affects Versions: 2.0.0
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: JCR-2042-poc.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.