That's because it doesn't really matter which prefix you use. It's
just XML. The important part is the namespace itself which is bound
to the prefix by a xmlns declaration.
Ingo
Hi,
Can someone do me the favour of answering this question.
Why when I connect to a IIS WebDAV server when i
: Ingo Brunberg [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 23, 2004 9:29 AM
To: [EMAIL PROTECTED]
Subject: Re: Property Namespaces question
That's because it doesn't really matter which prefix you use. It's
just XML. The important part is the namespace itself which is bound
to the prefix
Paul Hussein wrote:
It matters when I want to somehow determine which is a custom property and
which is not.
In IIS the system ones are prefixed with a:, and in slide d:.
Is there another way to determine what is a predefined system property, and
a custom one?
As already stated, the prefixes are
Namespaces question
Paul Hussein wrote:
It matters when I want to somehow determine which is a custom
property and
which is not.
In IIS the system ones are prefixed with a:, and in slide d:.
Is there another way to determine what is a predefined system
property, and
a custom one
Paul Hussein wrote:
Just automatic code to allow editing of custom properties and not system
properties.
Thanks for the input.
Well, there's no generic way to do that. As a matter of fact, a system
property may be editable (such as DAV:displayname), while a custom
property may be read-only; so
Hi,
Can someone do me the favour of answering this question.
Why when I connect to a IIS WebDAV server when i call property.getName() on
a property it is prefixed by 'a:' and for Slide it is prefixed by 'D:' when
I explicitly enter my namespace when creating the property.
Is there a standard