hi benjamin
the aim of the webdav server/client part in
jackrabbit was to provide a jackrabbit independant
implementation.
the dependencies to jackrabbit-core is limited to
helper classes (with one single exception that is marked
as 'to-be-reworked'), that i would wish where not part
of the core but part of some more general jackrabbit
package... on the other hand i didn't want to duplicate
code (or using yet another library) just for the sake
of being independant.
i recently provided a list of dependencies to the
jackrabbit-core-team (tobias). maybe we can find a solution
to detach the fundamental utility classes from the core.
regards
angela
Benjamin Mestrallet wrote:
> Hi
>
> After a discussion with David (http://www.theserverside.com/news/
> thread.tss?thread_id=33803) I have decided to test the jackrabbit
> WebDAV implementation on top of our eXo JCR.
>
> Unfortunately the code is not jackrabbit independant but the
> dependencies are not that big.
>
> For example in jcr-webdav there are some references to jackrabbit core
> classes like some constants and utils class to de/serialize and
> generate uuid.
>
> So my question is, would you be interested to make those tools (the rmi
> one is quite nice too) independent of the real implementation and make
> it only reference the JSR 170 API.
>
> If so, our team would be pleased to help you and contribute to be sure
> the tools work on both Jackrabbit and eXo JCR.
>
> Thanks
>
> Benjamin Mestrallet
>
|