Hi Daniel,
Many so called XML Schema validators are buggy when it comes to deal
with restriction and extension. As stated in the XML Schema
specification:
Schema Representation Constraint: Complex Type Definition Representation
OK
"2 If the <simpleContent> alternative is chosen, the type definition
.resolved. to by the .actual value. of the base [attribute] must be
either a complex type definition whose {content type} is a simple type
definition or, only if the <extension> alternative is also chosen, a
simple type definition; "
The section being 3.4.3 and not 4.3.3
Arnaud
> -----Original Message-----
> From: Daniel Shane [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 08, 2003 5:13 PM
> To: [EMAIL PROTECTED]
> Subject: [castor-dev] Restriction incorrect at line 153 of
> SimpleContentRestrictionUnmarshaller.java
>
>
> Hi,
>
> I believe there is a wrong interpretation of the XML Schema
> specification at line 153 of
> SimpleContentRestrictionUnmarshaller.java, maybe it dates
> from an older schema specification.
>
> Is states that :
>
> //we are now sure that the base is a ComplexType
> //but is the base of this complexType a simpleType?
> (see 4.3.3->simpleContent->content type)
>
> err += "In a simpleContent when using restriction the base type"+
> " must be a complexType whose base is a simpleType.";
>
> All current XML Schema validator accept my schema, so I tend
> to believe that this must be incorrect. Does anyone know of a
> quick fix to get rid of this condition?
>
> Thanks in advance,
> Daniel Shane
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
>
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
