That seems to be exactly what I was seeing. And it looks like
nonnamespace->namespace coercion and type redefinition is really working
properly--I had forgotten that global attribute definitions unlike local
ones required qualification under attributeFormDefault="unqualified".
Thanks,
Eric
George Cristian Bina wrote:
I get 2 contradictory errors validating an xml file using a
schema with this construct:
[Error] unittest.xml:2:154: cvc-complex-type.3.2.2: Attribute
'someAttr' is not allowed to appear in element 'test'.
[Error] unittest.xml:2:154: cvc-complex-type.4: Attribute
'someAttr' must appear on element 'test'.
See:
Contradictory validation messages
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24292
I have not checked your report in detail but I guess it is the same problem.
Best Regards,
George
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
