Hi folks,
This has probably been asked before, but I can't seem to access the
archives of the mail list, and I can't find a reference in any of the FAQs
Anyway, my question is this:
I have a method which is being called with a DOM Document, and I need to
serialize this DOM as XML an
1. src-import.3.1: ...
You provided 2 location hints for the namespace "http://foo/TruckTrace";,
one through xsi:schemaLocation with the value "TruckTrace.xsd"; one through
, with the value "TruckTraceSoap.xsd". The parser is free to pick
whichever one. Xerces decides to use "TruckTrace.xsd". But
Hello
Here are the schema that I try to use.
TruckTrace.xsd, TruckTraceSoap.xsd, TruckTraceRequest.xsd,
TruckTraceResponse.xsd.
TruckTrace.xsd
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
xml
>no part of the *unique* root element may appear anywhere else in the
document
That is not the intent of the language. The root element is not "unique"
in any sense except that of being the only top-level element in the
document.
>I'm fairly certain that in the past I've encountered DTDs that
Hi Joe,
I am well aware that multiple top-level elements are not allowed. I have
been using XML for about 2 years or so now and thought I was quite familiar
with it until a colleague asked why IE didn't break when he gave the sample
document I gave. I had read the W3C Recommendation several time
What is "not allowed" is for there to be more than one top-level element:
(with or without additional content within those elements, and no matter
what their names are), or indeed *anything* other than the XML
Declaration, doctype declaration, comments, PI's, and whitespace out
Andy,
Thank you. In other words, the wording in the W3C definition:
"...no part of which appears in the content of any other element."
refers to the 'physical' tag, not the tag name? If that's the case, then it
doesn't seem necessary to word it in such an ambiguous manner. As long as it
states th
Swanson, Brion wrote:
I just ran sax.Counter (Xerces 2.2.0) with the following input file:
This is a EmptyElemTag
see
http://www.w3.org/TR/REC-xml
search for EmptyElemTag
The xml is wellFormed
It worked completely fine and did not throw a SAXParseException. Is this a
well-formed document? I
Swanson, Brion wrote:
I just ran sax.Counter (Xerces 2.2.0) with the following input file:
It worked completely fine and did not throw a SAXParseException. Is this a
well-formed document? I would think not based on the W3C definition:
[Definition: There is exactly one element, called the ro
Daniel Rabe wrote:
I'm using SAX (Xerces 2.3.0 on Windows XP) to parse an XML file that can
contain large CDATA sections (where large is somewhere between 1 and 5
Mb). The data is Base64-encoded. The code works properly, but when the
CDATA is over 1Mb or so, it's very slow. It seems like a 1Mb C
10 matches
Mail list logo
