Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <771100965.1253228037560.JavaMail.jira@brutus>
Date: Thu, 17 Sep 2009 15:53:57 -0700 (PDT)
From: =?utf-8?Q?Michael_D=C3=BCrig_=28JIRA=29?= <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-2042) RepositoryFactory implementation for
 jcr2spi
In-Reply-To: <378226727.1237988452185.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Michael D=C3=BCrig updated JCR-2042:
-------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Fixed in revision: 816402

> 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
>            Assignee: Michael D=C3=BCrig
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: JCR-2042-poc.patch
>
>
> There should be a RepositoryFactory implementation in jcr2spi that also c=
overs acquiring the underlying RepositoryService.
> For this purpose I suggest to create:
> -  a RepositoryServiceFactory in jackrabbit-spi, which encapsulates the s=
pi implementation specifc instantiation of the RepositoryService. the facto=
ry probably just needs a single method that takes a parameters map.
> - a RepositoryFactory implementation in jcr2spi, which works with a URI t=
hat contains all required information to connect/acquired the RepositorySer=
vice.
> To use jcr2spi/spi2jcr/jackrabbit-core:
> - jcr+file://path/to/repository/home?config=3Drepository.xml
> To use jcr2spi/spi2dav:
> - jcr+dav://localhost:8080/server/repository/?br=3D4
> To use jcr2spi/spi2davex:
> - jcr+davex://localhost:8080/server/repository/
> An implementation of RepositoryServiceFactory must check the scheme and d=
ecide 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.

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