jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-2453) Break the spi2dav dependency to jcr-server
Date Wed, 29 Sep 2010 14:11:37 GMT

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

angela resolved JCR-2453.

    Fix Version/s: 2.2.0
       Resolution: Fixed

> Break the spi2dav dependency to jcr-server
> ------------------------------------------
>                 Key: JCR-2453
>                 URL: https://issues.apache.org/jira/browse/JCR-2453
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jcr-server, jackrabbit-spi2dav, jackrabbit-webdav
>            Reporter: Jukka Zitting
>            Assignee: angela
>             Fix For: 2.2.0
>         Attachments: JCR-2453.patch
> Currently the spi2dav component has a dependency on the jcr-server component, which is
troublesome due to the extra transitive dependencies and which strictly speaking should not
be necessary from an architectural point of view.
> The dependency exists mostly for sharing a number of JCR-specific WebDAV constants. I'd
like to push those constants down to jackrabbit-webdav as they are essentially just shared
strings and as jackrabbit-webdav already contains a number of constants used by JCR extensions.
> In addition to constant values, code in the following classes is shared between jcr-server
and spi2dav: JcrValueType, NamespacesProperty, NodeTypesProperty, SearchResultProperty, SubscriptionImpl,
ValuesProperty. The shared code in JcrValueType and SubscriptionImpl is mostly just about
mapping constant value mappings and could fairly easily be moved to jackrabbit-webdav. The
Property classes are a but trickier, but it looks like it would be possible to split the code
to separate server- and client-side classes for jcr-server and spi2dav.

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

View raw message