any processContents= "skip " 2003-01-16 - By sandygao@(protected)
Your root element is called "AuthnRequestEnvelope", whose type is defined
as
<element name="AuthnRequestEnvelope" type
="lib:AuthnRequestEnvelopeType"/>
<complexType name="AuthnRequestEnvelopeType">
<complexContent>
<extension base="lib:RequestEnvelopeType">
<sequence>
<element ref="lib:AuthnRequest"/>
<element ref="lib:ProviderID"/>
<element name="ProviderName" type="string"
minOccurs="0"/>
<element name="AssertionConsumerServiceURL"
type="anyURI"/>
<element ref="lib:IDPList" minOccurs="0"/>
<element name="IsPassive" type="boolean"
minOccurs="0"/>
</sequence>
</extension>
</complexContent>
</complexType>
And the type "RequestEnvelopeType" is defined as
<complexType name="RequestEnvelopeType">
<sequence>
<any processContents="skip" minOccurs="0" maxOccurs
="unbounded"/>
</sequence>
</complexType>
So the result of the type "AuthnRequestEnvelopeType" is any number of any
elements from any namespace, followed by a sequence of "AuthnRequest",
"ProviderID", ... This violates the "Unique Particle Contribution"
constraint [1], because it causes ambiguity.
You'll see an error reported against such violation if you turn on the
"schema-full-checking" feature [2], which is off by default, for
performance concerns.
[1] http://www.w3.org/TR/xmlschema-1/#cos-nonambig
[2]
http://xml.apache.org/xerces2-j/features.html#validation.schema-full-checking
HTH,
Sandy Gao
Software Developer, IBM Canada
(1-905) 413-3255
sandygao@(protected)
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)
|
|
