Issue 153 in genxdm: Validator failing when processContents is skip, but unresolvable xsi:type is present

[gen...@googlecode.com]

Status: New
Owner: joe.bays...@gmail.com
Labels: Type-Defect Priority-Medium Milestone-Release1.1
Component-Processors

New issue 153 by joe.bays...@gmail.com: Validator failing when
processContents is skip, but unresolvable xsi:type is present
http://code.google.com/p/genxdm/issues/detail?id=153

If a wildcard's processContents is set to skip, but a child has an xsi:type
attribute that's unresolveable, we're raising an exception for the
unresolved xsi:type. We should not.


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[gen...@googlecode.com]

Updates:
Status: Fixed

Comment #1 on issue 153 by joe.bays...@gmail.com: Validator failing when

processContents is skip, but unresolvable xsi:type is present
http://code.google.com/p/genxdm/issues/detail?id=153

r503. Ignore unresolved xsi:types if processContents is skip or lax.

[gen...@googlecode.com]

Updates:
Status: Started

Comment #2 on issue 153 by joe.bays...@gmail.com: Validator failing when

processContents is skip, but unresolvable xsi:type is present

https://code.google.com/p/genxdm/issues/detail?id=153

Re-opening this ticket because we're still failing on the following use
case: element w/unresolveable xsi:type attribute matches a wildcard (in
its parent content model) whose processContents is set to skip or lax. In
that case, we're still incorrectly reporting an error.

[gen...@googlecode.com]

Updates:
Status: Fixed

Comment #3 on issue 153 by joe.bays...@gmail.com: Validator failing when

processContents is skip, but unresolvable xsi:type is present
https://code.google.com/p/genxdm/issues/detail?id=153

r517. AttributeManager.initialize(...) now returns a QName for unresolved
xsi:types instead of a boolean. That QName is non-null only if an xsi:type
is not resolveable. ValidationKernel.startElement now reports an error if
AttributeManager.initialize returns a QName (see above) and the current
processContents is strict.