jharrop | 7 Apr 03:05

RE: The state of WebDAV Clients


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  where it can be
maintained/enhanced as necessary.  

The new name is intended to convey that this can (or rather, will, depending
on contributions) interoperate with a variety of webdav servers.

>  I'm willing to invest
> some effort into that next year, after we've
> completed the HttpComponents move to TLP. But
> at the moment, I don't see too many people working
> on a WebDAV client. If you know any, please send
> them our way :-) The best starting point for now
> would be the Jackrabbit client code that is just
> waiting for somebody to release it.
> 
> Of course you can always continue to use the
> Slide WebDAV client. There wasn't much support
> for some time, so the situation didn't really
> change by the retirement. It is now just obvious
> to anybody that the code is unsupported.
> 
(Continue reading)

jharrop | 7 Apr 03:12

Re: Alternative webdav client api?


Roland Weber wrote:
> 
>> Is there a natural migration path for my situation?
> 
> If all you use is the client, there is no immediate hurry. However,
> the Slide WebDAV client is based on an unsupported backlevel version
> of HttpClient, besides being unsupported itself. As long as it works,
> you're fine. As soon as a problem occurs, you're on your own.
> 
> The Jackrabbit WebDAV client is your best option at Apache.
> I don't know about any non-Apache WebDAV clients.
> 

I've uploaded the slide webdav client code to
https://sourceforge.net/projects/webdavclient4j  where it can be
maintained/enhanced as necessary.

I've replaced the unsupported HttpClient with the newer 3.0.1 client.
--

-- 
View this message in context: http://www.nabble.com/Alternative-webdav-client-api--tp13885439p16532022.html
Sent from the Jakarta Slide - User mailing list archive at Nabble.com.
Picon

Re: Alternative webdav client api?

Good initiative :)

Eirikur S. Hrafnsson
Chief Software Engineer
Idega Software
http://www.idega.com

On Apr 7, 2008, at 1:12 AM, jharrop wrote:

>
>
> Roland Weber wrote:
>>
>>> Is there a natural migration path for my situation?
>>
>> If all you use is the client, there is no immediate hurry. However,
>> the Slide WebDAV client is based on an unsupported backlevel version
>> of HttpClient, besides being unsupported itself. As long as it works,
>> you're fine. As soon as a problem occurs, you're on your own.
>>
>> The Jackrabbit WebDAV client is your best option at Apache.
>> I don't know about any non-Apache WebDAV clients.
>>
>
> I've uploaded the slide webdav client code to
> https://sourceforge.net/projects/webdavclient4j  where it can be
> maintained/enhanced as necessary.
>
> I've replaced the unsupported HttpClient with the newer 3.0.1 client.
> -- 
(Continue reading)

Michael Burkhardt | 29 Apr 01:12
Picon

accessing Exchange 2003

Hello,

first of all, sorry for my English. Second, I'm using WebDAV since last friday.
But I have some problems to learn WebDAV.

I'm trying to connect to an Exchange server. Therefor I read on MSDN some
articles and use the examples from there, e.g.
http://www.msexchange.org/articles/Access-Exchange-2000-2003-Mailbox-WebDAV.html .

I tried to understand the example and execute it. Then I tried to make this
example with Java and Slide, but all the time I get an UnknownHostException when
I use a SearchMethod with query. If I just connect and disconnect like this

HttpURL httpURL = new HttpURL(...);
WebdavResource webdavResource = new WebdavResource(httpURL);
webdavResource.disconnect();

everything is fine.

May some of you guys have a little example with Slide for me to connect to a MS
Exchange server? That would be great.

Thanks a lot.

Ciao, Micha

Gmane