I finally sat down and did schema validation, because <xmlvalidate> couldnt handle the complexity of namespaces very well, and I had a pressing need to do things.
1. Moderate refactoring of XMLValidateTask to get it all to work; a few places where careful subclassing can integrate with this (fairly complex) task.
You can also use the JARV task: http://iso-relax.sourceforge.net/JARV/antTask.html
2. I create my own XML parser factory. I dont know if this is really needed; the docs were inconsistent. Particularly JAXP1.3 says you had better ask for validating and namespace aware. So I did.
NB: xmlvalidate docs say it is not namespace aware by default. I think it is now, as the factory is.
3. An inadequate number of tests. I'll add more as I use it, but more are welcome.
4. No running of these inadequate tests on anything other than Xerces .
Do we ever test ant with other XML Parsers? I'd like to try it on Java-5-retail , as it were; to see what sun broke.
JAXP1.3 says it ships with rudimentary xinclude support. Is this true? Does xerces handle it as well, or is it just a xalan thingy. I'd like an XInclude task if we could pull it off, to make my fairly complex xml workflow tractable (building up WSDL files from multiple XSDs).
Xerces handles the XInclude. You can take advantage of it by setting the system property:
org.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.XIncludeParserConfiguration
best, -Rob
-steve
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
