Hi Jorge, I did try to work on this bug report. >From my point of view, I can confirm that this seems to be indeed a bug. But it doesn't appears to be specific to Xerces's XSD 1.1 <assertion> implementation. Without the <assertion>, the codebase exhibits the same bug and it is present within both Xerces XSD 1.1 and 1.0 implementations. I've attempted to fix it and the changes for this have been committed to SVN. Kindly verify if the fix looks fine.
On Wed, Apr 4, 2012 at 6:36 AM, Mukul Gandhi <muk...@apache.org> wrote: > Hi Jorge, > > On Tue, Apr 3, 2012 at 11:05 PM, Jorge Williams > <jorge.willi...@rackspace.com> wrote: >> You shouldn't need to define X at all, right? > > I think declaration for element "X" in an XSD schema in this case, > would certainly be required (i.e xs:element ... etc) for an XML > instance element to be considered valid. > >>...or am I missing something? If you remove >> >>> <xs:element name="X" type="xs:integer"/> >> >> from your schema, you'll see the same issue I am....the XML appears valid >> but it's not. > > From a quick look, it seems to me that when xsi:type is present in an > XML instance element (and the XSD type pointed by xsi:type has an > xs:assertion) and if this instance XML element doesn't have a > corresponding xs:element declaration in the schema, the validation > still passes. It doesn't look like a issue of xs:assertion not working > correctly when the type comes from xsi:type (my example demonstrates > this), but there looks a different issue which needs to be > investigated. Thanks for creating a Jira bug -- it'll be actioned > appropriately. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org For additional commands, e-mail: j-users-h...@xerces.apache.org
