[
https://issues.apache.org/jira/browse/JCR-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-2451:
-------------------------------
Fix Version/s: 2.0.0
Summary: Implement RepositoryFactory in jcr2dav (was: Implement
RepositoryFactory in spi2dav)
Adjusted subject: s/spi2dav/jcr2dav/
Agreed about the dislike for such a small component. It however seems like the
easiest way forward especially since I'd like to have this included already in
2.0 and I'd prefer to avoid making too big changes to our component structure
at this point.
> Implement RepositoryFactory in jcr2dav
> --------------------------------------
>
> 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
> Fix For: 2.0.0
>
> 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.
