any processContents= "skip " 2003-01-17 - By Sandy Gao/Toronto/IBM
> What's the solution then? The schema is not correct?
Right, I meant your schema isn't correct. It results in something like (a?
a), which is an ambiguous content model. How to fix it is up to you,
depending on how you want your content model to look like.
Sandy Gao
Software Developer, IBM Canada
(1-905) 413-3255
sandygao@(protected)
"Evaristo-Jose Camarero
(ECE)" To: "'xerces-j
-user@(protected)'" <xerces-j-user@(protected)>
<Evaristo-Jose.Camarero@(protected) cc:
ricsson.se> Subject: RE: any
processContents="skip"
01/17/2003 04:26 AM
Please respond to
xerces-j-user
Hi Sandy again:
You are right, I obtain the following error:
Exception in thread "main" org.xml.sax.SAXParseException:
cvc-complex-type.2.4.b: The content of element 'AuthnRequestEnvelope' is
not complete. It must match '(((WC[##any]){0-UNBOUNDED}),(("
http://projectliberty.org/schemas/core/2002/12":AuthnRequest),("
http://projectliberty.org/schemas/core/2002/12":ProviderID),("
http://projectliberty.org/schemas/core/2002/12":ProviderName){0-1},("
http://projectliberty.org/schemas/core/2002/12
":AssertionConsumerServiceURL),("
http://projectliberty.org/schemas/core/2002/12":IDPList){0-1},("
http://projectliberty.org/schemas/core/2002/12":IsPassive){0-1}))'.
What's the solution then? The schema is not correct?
Regards and thanks,
Evaristo
Ericsson R&D
> -----Original Message-----
> From: sandygao@(protected) [mailto:sandygao@(protected)]
> Sent: Thursday, January 16, 2003 5:34 PM
> To: xerces-j-user@(protected)
> Subject: RE: any processContents="skip"
>
>
> 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.schem
a-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)
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)
|
|
