> I'd like to know what is the level of stability of the
> current slide release (M8).
As a whole, it's not feature complete, so it can be considered alpha
software.
> Also, when moving files between two collections, the files
> are logically moved from one collection to the other. But
> physic
Hi,
Can somebody explain how Slide interpetes the mapping URIs to Namespaces
Nodes and further to URLs.
Say, RFC 2396 defines URI like: "schema://server(authority)/path/query". And
URI in RFC 2518 is considered just as a name that is supposed to map to the
Resource Model Namespace and then furth
Hi,
I'd like to know what is the level of stability of the
current slide release (M8).
Also, when moving files between two collections, the files
are logically moved from one collection to the other. But
physically on disk, the source file remains there.
So when one try to put the same file
> Is there any client exemple written using this api, or other documentation
> about the client api other than the JavaDoc? We searched the web site but
> found nothing.
>
> Thank you for your time and have a nice day!
You should have a look at the old command line client
(src/webdav/client/org/a
> Thanks Remy,
> For DAV:resourcetype
> Another question:
> After using propFindMethod.getResponseProperties(url), For the property
> resourcetype, The getPropertyAsString() method gives "" even for
collection
> resource type.
> the reply xml fragment is :
>
>
> Could we find a way to distingu
Thanks Remy,
For DAV:resourcetype
Another question:
After using propFindMethod.getResponseProperties(url), For the property
resourcetype, The getPropertyAsString() method gives "" even for collection
resource type.
the reply xml fragment is :
Could we find a way to distinguish collection an
