=?ISO-8859-1?Q?Re=3A=20=27Re=3A=20=22=5Bxml=5D=20Schema=20validation=20failing=20for=20xs=3Aall=20element=22=27?=



Hi,

on 9/22/2004 11:42 AM Stuart Dootson wrote:

On Wed, 22 Sep 2004 11:36:31 +0200, Kasimier Buchcik
<kbuchcik 4commerce de> wrote:

Hi,

on 9/22/2004 10:33 AM Stuart Dootson wrote:

I have a schema which has an xs:all construct. XML files written
against this validate at libxml2 2.6.11, but not at 2.6.12/13. The
validation fails in 2.6.12/13 with the error:

Schemas validity error : Element 'x:a' [CT local]: The element
content is not valid.

[...]

Yes, the bug is definitely on libxml2's schema processor side :-(
Feel free to bugzilla it 

OK - I'd assumed it was a regression, as 2.6.11 appeared to correctly
validate the files (and fail validation when the element content was
malformed).

No, as of 2.6.11 the schema processor did not take namespaces into 
account during the validation of the content model; namespace awareness 
was activated in ver. 2.6.12.

I'll enter it into Bugzilla.
Cool.

It's already fixed, but I will need some time (a day?) to commit.

Thanks & regards,

Kasimier




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]