How can I use PropFindMethod?

I want to use PropFindMethod to retrieves my interesting properties of the
file. When I used this, it didn't send XML properties name that I want to
the server.
My code like this,

       HttpClient http = new HttpClient();
*

>        Credentials credentials = new
> UsernamePasswordCredentials(SERVER_USERNAME, SERVER_PASSWORD);
>        http.getState().setCredentials(new
> AuthScope(SERVER_HOST,SERVER_PORT), credentials);
>        http.getParams().setAuthenticationPreemptive(true);
>        HostConfiguration hostConfig = new HostConfiguration();
>        hostConfig.setHost(SERVER_HOST, SERVER_PORT, SERVER_PROTOCAL);
>        PropFindMethod propFindMethod = new PropFindMethod();
>        propFindMethod.setDepth(DepthSupport.DEPTH_0);
>        propFindMethod.setPath(CALDAV_SERVER_WEBDAV_ROOT);
>        propFindMethod.setType(PropFindMethod.BY_NAME);
>        Vector<PropertyName> v = new Vector<PropertyName>();
>        v.add(new PropertyName("DAV", "resourcetype"));
>        v.add(new PropertyName("DAV", "calendar-home-set"));
>        propFindMethod.setPropertyNames(v.elements());
>        status = http.executeMethod(hostConfig, propFindMethod);
>        System.out.println(status);
>

But I found that my code didn't send properties "resourcetype" and
"calendar-home-set" to the server it only sent the header?
Is my code wrong?

Thank you.

Setting PR_CONVERSATION_INDEX

Hi all,

I'm trying to do a seemingly simple task of setting the
PR_CONVERSATION_INDEX  (PidTagConversationIndex) on my item before I send my
email out. I've tried to set other MAPI properties like PR_COVERSATION_TOPIC
using the proppatch method and they seem to go through fine. But for
PR_CONVERSATION_INDEX this doesn't quite fly since that property is of type
PT_BINARY. Looks like Slide's proppatch method is quite restrictive, as in
it requires that the value of the MAPI property you set is of type String.
So since PR_CONVERSATION_INDEX is of type PT_BINARY, things seem to not work
out in this case. Can anyone help out and let me know of a way to tackle
this issue?

One alternative that I was considering was to use Exchange Web Services
(EWS). Does anyone know if the same end can be achieved by using EWS? And if
so, how should I go about it?

All responses will be greatly appreciated.

Thanks,

Nitin
--

-- 
View this message in context: http://www.nabble.com/Setting-PR_CONVERSATION_INDEX-tp23052149p23052149.html
Sent from the Jakarta Slide - User mailing list archive at Nabble.com.

configure a namespace for each user

Hello,

 I'm a new user of slide and I'd like to configure the namespace to create a
namespace for each user defined in Domain.xml. I don't wanna  justa create a
folder for each user, but I want that the users use the same path to save
the files and that files are saved in his own folders.

I´m searching for it in the API, in the jakarta slide page and in the
google.

Someone know how to solve this problem?

thanks!!!

--

-- 
"Que homem é aquele que não pode fazer do mundo um lugar melhor"

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

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.
> 

--

-- 
View this message in context: http://www.nabble.com/The-state-of-WebDAV-Clients-tp13950123p16531993.html
Sent from the Jakarta Slide - User mailing list archive at Nabble.com.

Re: The state of WebDAV Clients

How scalable is the slide in terms of storage.

Hello All,

We use the slide 2.1 milestone 1 as our repository solution.  
Recently we have faced an issue with the storage space.

With the large number of content of size around 500 MB each, the storage
space on single disk falls short.

Slide provides multiple stores.  We thought to leverage it for
supporting multiple disks with each store pointing to a new disk.

Unfortunately what you found is that for versioning support the root
store is always used.  In other words, all versions of any resource
located in any store are stored in the root store.  It defeats the sole
purpose of having multiple stores.

Is there anybody who can validate the above observation and if incorrect
suggest me a way to configure slide for storage space extensibility?

Also pointers on any other issues that might arise from such
configuration such as caching, transactions, etc are greatly
appreciated.

Regards,

Abhijeet
Technical Architect
Saba Software

The state of WebDAV Clients

I am a bit concerned at the state of WebDAV client implementations in Java.

The slide project has been recently retired and Apache recommends
using JackRabbit as an alternative.
JackRabbit does not currently have a WebDAV client implementation
according to this post
(http://www.nabble.com/Webdav-Client-Examples--tf4803755.html#a13852979).
Others in the industry like Eclipse, are using slide as the basis for
their new EFS WebDAV implementation
(http://wiki.eclipse.org/WebDAV_EFS_Implementation).

In all of my searching, I have yet to find a viable alternative to
slide as a WebDAV client. I think it is clear that there is a need for
a project like this. Has there been any though in starting an Apache
Commons project to provide WebDAV support? My understanding was that
the Slide client was stable and would probably provide a good starting
point for a WebDAV client.

For more information on my WebDAV research see this post:
http://pragmaticchris.blogspot.com/2007/11/java-webdav-clients.html

Thanks

Chris Dail
http://pragmaticchris.blogspot.com

Alternative webdav client api?

Hi,

the retirement announcement for Slide, mentions Jackrabbit as an alternative
to slide.
I am mostly interested in using the api to access an existing WebDav
repository, but
it seems Jackrabbit is mostly focused on the server side of webdav, not the
client.

Is there a natural migration path for my situation?

Thanks in advance for any help,

Florian
--

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

[ANNOUNCEMENT] Jakarta Slide is retired

The Apache Jakarta PMC is sorry to announce the retirement
of the Jakarta Slide subproject. After it's last release in
December 2004, development activity was significantly reduced
and came to a total standstill this year. Without a minimum
developer community that can release security fixes, we have
no choice but to retire Slide. We'll keep at least one of
the mailing lists open for a transition period, so users can
discuss alternatives and migration away from Slide. Further
use of the Slide codebase is discouraged.

One alternative to Slide is provided by the Apache Jackrabbit
project. Jackrabbit has a healthy, active developer community
and provides, among others things:
- a server-side content repository
- a WebDAV server component for access to the repository
- a WebDAV client component
Please visit http://jackrabbit.apache.org/ for more information.

We apologize for the inconveniences.

Roland Weber
  (wearing an Apache Jakarta PMC hat)

[ANNOUNCEMENT] Jakarta Slide is retired

The Apache Jakarta PMC is sorry to announce the retirement
of the Jakarta Slide subproject. After it's last release in
December 2004, development activity was significantly reduced
and came to a total standstill this year. Without a minimum
developer community that can release security fixes, we have
no choice but to retire Slide. We'll keep at least one of
the mailing lists open for a transition period, so users can
discuss alternatives and migration away from Slide. Further
use of the Slide codebase is discouraged.

One alternative to Slide is provided by the Apache Jackrabbit
project. Jackrabbit has a healthy, active developer community
and provides, among others things:
- a server-side content repository
- a WebDAV server component for access to the repository
- a WebDAV client component
Please visit http://jackrabbit.apache.org/ for more information.

We apologize for the inconveniences.

Roland Weber
  (wearing an Apache Jakarta PMC hat)