There has to be a simplier way to get the namespaces to work. My own
custom modfications uses the apache XPathAPI interface, that resolves
space for you.
The JAXP 1.3 NamespaceContext is almost a kludge. While I know it
allows for parser independant implementations, it also requires you to
know the namespaces ahead of time. I figure XMLUnit should at least if
you specify that you want to use namespaces, that it automatically pulls
from the DOM the namespaces that have been defined and the prefixes
defined in the XML document. As it is now, unless I'm missing
something, the XMLAssert static functions still aren't namespace aware,
because they directly instantiate the newXpathEngine() method, which
doesn't set a NamespaceContext when it is created.
Also, there should be a way for the engine to be established once, and
reused, instead of being created each time. A few of these enhancements
would go a long way to help improve useability of the framework.
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
