Daniel,These two snippets are semantically equivalent: foobarand
foobar
If their parser can't process them both, it's seriously flawed.AnneOn 4/19/06, Daniel Destro <
[EMAIL PROTECTED]> wrote:I understand.This must be because I started to use LITERAL style instead of ENCODED, right?
My Web S
I understand.This must be because I started to use LITERAL style instead of ENCODED, right?My Web Service consumer is complaining about the lack of "ns1". They did a SOAP parser themselves, which is not good. I told them to follow the SOAP standard, otherwise they are going to have millions of prob
A namespace declaration that specifies a prefix (e.g., xmlns:foo="urn:foo.bar") allows you to refer to that namespace by its declared prefix ("foo"). A namespace declaration that does not specify a prefix (
e.g. xmlns="urn:foo.bar") establishes a default namespace. Any element within the scope of s
What is the difference between the two namespacesxmlns="urn:SacSilog"andxmlns:ns1="urn:SacSilog">Why one or other?thanks