On 2011-03-16, Andy Stevens wrote: > Or, since the jaxp13.Validator in v1.3 says it can handle a variety of > schema languages, is this error not being produced by XMLUnit anyway > but by whatever default SchemaFactory it's using?
I think so. > And if so, is there anything I can do about it? (e.g. a configuration > setting I can pass through to the SchemaFactory somehow) Honestly, I don't know. If you find some sort of property that would make your SchemaFactory instance happy, you can use the Validator-constructor that accepts a SchemaFactory argument and pass in your fully configured factory. > Oh yes, I forgot to mention, I'm using IBM's 1.6 JDK (in case that has a > bearing on the SchemaFactory that will be present) although I suppose I > could potentially run under any other Windows JDK if that would solve the > problem more easily. I've commited a simple testcase that uses "foo" as prefix rather than "xsd" to XMLUnit's svn tree[1] and it passes on my Windows7 machine using Oracle's JDK 6 (.23) as well as the OpenJDK7 milestone (not quite the latest) that I have installed. Stefan [1] http://xmlunit.svn.sourceforge.net/viewvc/xmlunit?view=revision&revision=491 ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Xmlunit-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xmlunit-general
