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 2010/01/06 18:39:55 UTC

[jira] Commented: (JCR-2451) Implement RepositoryFactory in spi2dav

    [ https://issues.apache.org/jira/browse/JCR-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797194#action_12797194 ] 

Michael Dürig commented on JCR-2451:
------------------------------------

+1 for the updated patch (jcr2dav module) for 2.0 

However I think we should discuss/riview the overall module structure in general for future releases. 

> Implement RepositoryFactory in spi2dav
> --------------------------------------
>
>                 Key: JCR-2451
>                 URL: https://issues.apache.org/jira/browse/JCR-2451
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jcr-commons, jackrabbit-jcr2spi, jackrabbit-spi2dav
>            Reporter: Jukka Zitting
>         Attachments: JCR-2451.patch, JCR-2451.patch
>
>
> It's currently a bit cumbersome to set up a spi2dav instance because of the two levels of factories (RepositoryFactory & RepositoryServiceFactory) involved in the process. It would be easier if spi2dav implemented RepositoryFactory directly, so downstream users would only need to provide the server URI parameter instead of specifying also the RepositoryServiceFactory classname.
> To do this, spi2dav would need to depend also on jcr2spi. This change would actually simplify downstream projects, that then wouldn't need to depend also to jcr2spi to get JCR -> DAV connectivity.

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