You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/01/06 14:02:54 UTC
[jira] Created: (JCR-2451) Implement RepositoryFactory in spi2dav
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
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.
[jira] Commented: (JCR-2451) Implement RepositoryFactory in spi2dav
Posted by "Thomas Mueller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797279#action_12797279 ]
Thomas Mueller commented on JCR-2451:
-------------------------------------
I agree that the overall module structure should be revised as soon as possible.
Creating a new project that contains one class is strange.
> 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.
[jira] Updated: (JCR-2451) Implement RepositoryFactory in jcr2dav
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (JCR-2451) Implement RepositoryFactory in spi2dav
Posted by "Michael Dürig (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (JCR-2451) Implement RepositoryFactory in spi2dav
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-2451:
-------------------------------
Attachment: JCR-2451.patch
I discussed this with Angela and Michael at work, and we thought it best to keep the current scope of the spi2dav component and introduce a separate jcr2dav component that contains the proposed RepositoryFactory class.
See the updated patch for the proposed new component.
> 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.
[jira] Updated: (JCR-2451) Implement RepositoryFactory in spi2dav
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-2451:
-------------------------------
Attachment: JCR-2451.patch
Proposed patch.
> 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
>
>
> 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.
[jira] Resolved: (JCR-2451) Implement RepositoryFactory in jcr2dav
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-2451.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.0.0)
2.0-beta6
Assignee: Jukka Zitting
The jackrabbit-jcr2dav component now exists in trunk and the 2.0 branch. Resolving as Fixed.
> 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
> Assignee: Jukka Zitting
> Fix For: 2.0-beta6
>
> 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.