Roland Weber wrote:
Users of the current Slide codebase are welcome
to fork and support the code. They are even more
welcome to form a new project to move away from
the HttpClient 2.x/3.x API.
I've uploaded the slide webdav client code to
https://sourceforge.net/projects/webdavclient4j
Thank you for your answers Arne and Roland,
But what do you think?
Because our project wants to have additional WebDAV capacities I'd
prefer extend a existing server coming form a active community and not
fork from jackrabbit or slide WebDAV server and maintain this one.
Do you think this
Hi Raymond,
we have to face the facts: Many people are interested in using a
WebDAV-Server and Client-Lib that can be integrated easily in their
projects, but no one (or only one - hi oliver ;-) ) is implementing it.
The developer who should now help jackrabbit developers to implement a
Their simple or default WebDAV server. That doesn't mean it can't
be extended to JSR-170 + additional APIs for addressing additional
functionality. Of course that's something that would need to be
developed.
I agree with you. But that is not in the interest of the
Jackrabbit-Developers.
Hi,
About: “Oliver made a fix in Subversion, but there was nobody who could
release a fixed Slide, either as a minor update to the last Slide
release years ago, or as a new release of the current code in Subversion.”
In ESUP-Portail project we have made a lot of work over Slide. Perhaps
Hi,
us you read the answer to my question in the Jackrabbit User-mailing
list you know, that jackrabbit does not want to replace slide. It is
focused on the jsr-170 compatible store and not on webdav. (No ACLs, no
Events, no Bindings) And this can't change, because their webdav server
should run
Arne v.Irmer wrote:
[...] jackrabbit does not want to replace slide. It is
focused on the jsr-170 compatible store and not on webdav. (No ACLs, no
Events, no Bindings) And this can't change, because their webdav server
should run on any jsr-170-container.
Their simple or default WebDAV
Hello Chris,
JackRabbit does not currently have a WebDAV client implementation
according to this post
(http://www.nabble.com/Webdav-Client-Examples--tf4803755.html#a13852979).
The way I read this post, they have the implementation.
It is just not released as a separate component.
The
