Well, it seems that if you use the XMLUnit.setNamespaceContext, it will carry across when it gets the XPath engine. I haven't taken a look yet, but is there a way to specify which XPath engine to use, as we can with the SAX and DOM parsers? It would be nice to be able to specify either JAXEN, XALAN, or SAXON's xpath engines. Particularly if you are trying to verify that something works across the various XPath engines available.Note that I don't like the XMLUnit with lots of statics API myself either. I opted for API consistency when I added new things for the 1.1 release, but I plan to experiment with a different approach for XMLUnit 2.0. Your input is and will be more than welcome.
Also, there was mention of schema validation. Is this just validating an xml instance, or is this validating the xml schema it self?
Dave
begin:vcard fn:David Carver n:Carver;David org:STAR Standard adr;dom:;;4670 Wyandotte Dr;Columbus;OH;43230 email;internet:[EMAIL PROTECTED] title:XML Data Architect tel;work:614-397-1313 tel;fax:skype: kingargyle tel;home:614-475-7753 tel;cell:614-397-1313 x-mozilla-html:FALSE url:http://www.starstandard.org/ version:2.1 end:vcard
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ Xmlunit-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xmlunit-general
