Robert,
If the xerces implementation in witango, is validating to the nth
degree, don't you think it should be torqued down a bit, or maybe a
parameter in the <@dom> tag to allow strict or a non strict
implementation?
This is not about nth degree. There is no such thing in any of the
XML standards. It is simply about validating XML against a schema.
Namespaces and schemas are there for the very reason of validation.
By stripping them out you run the very real possibility of having
ambiguous elements, invalid XML or returning nodes that should not be
returned. Just because RB and VB do not validate the XML does not
make them correct. Maybe they just found it easier or faster to
implement a non validating parser. I would prefer to know the XML I
have is correct when it is parsed rather than just know that it will
parse.
Cuz the issue is, many of us have seen witango error on xml that
parse fine elsewhere, and so we take the approach, "You can't trust
witango to parse xml reliably", and find other workarounds. With
the current method, we would have to create a bean or something to
test xml for encoding issues, then xml validity, before passing to
xml. Which is why I had to write the witangoxmlcleaner bean.
Please send me a test case for XML that has issues with encoding.
As for validating XML I would recommend correcting the XML and
schemas you are using rather than skipping over errors in the XML or
schemas. The attitude of "You can't trust witango to parse xml
reliably" was born from a crap parser that had workarounds for this
and that to allow it to parse bad XML. So now we implement a
validating parser that errors when it should and you whack us with
"You can't trust witango to parse xml reliably" again. So you
actually want a parser that will validate when the XML and schema are
correct and not validate and parse when it is incorrect. Maybe you
should be asking the Xerces project for this feature in a future
release. I would love to see their response to the request.
You said, look at the readme, and we can see what library witango
uses, Also, "read the xerces manual".
No Ben suggested that. I suggested reading the XPath documentation
to get a better understanding of how to reference namespaces in xpath
expressions.
But we have no idea how you have implemented xerces in witango, and
I have shown the same library will parse this xml. So our only
recourse, is pull your head out of your hair trial and error.
It is not about how Xerces is implemented it is about a basic
principle of XML. All you have shown is that if you do not implement
the parser completely the validator does not kick in and it will
parse XML without checking the schema that it references. The xerces
parser as implemented in Witango 5.5 is following the XML rules. If
a schema is referenced then get it and validate the XML against it.
If you do not want the XML to validate don't reference a schema.
Easy as that. It has nothing to do with Witango documentation, this
is basic XML 101 stuff.
Robert, this discussion can go on forever about how you want us to
implement the xerces parser. In the end if your XML is correct and
your schemas are correct then the xerces parser as implemented in
Witango 5.5 will parse it.
Regards
Phil
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
