Hi
On 13/01/12 21:42, hdave wrote:
Thanks for the reply.
Would you agree that XML payloads, if they have anything, contain only a
reference to a namespace?
Yes
I guess, from this namespace, one could infer the XML schema, provided there
are not 2 or more schemas that constrain the namespace. It just seems like
greater precision would be called for...like it is in SOAP.
What I was saying that a specific client that expects say '<bar
xmlns:="http://bar"/>' needs to have an idea (in the configuration, etc)
of the schema referenced by "http://bar";, for example if it needs to
validate or say for JAXB to read the payload properly.
I'm not sure non-generic clients should rely on xsi:schemaLocation being
available in order to validate etc.
The other reason why xsi:schemaLocation is not recommended in the actual
payloads is that it makes it more difficult to use the alternative
schema languages, such as RelaxNG, it's not that big of deal for many
cases where use just go with XMLSchema, but either way, this attribute
makes the payloads schema-'unportable' :-)
Cheers, Sergey
--
View this message in context:
http://cxf.547215.n5.nabble.com/XML-Schema-and-REST-tp5140807p5143824.html
Sent from the cxf-user mailing list archive at Nabble.com.
