[ 
https://issues.apache.org/jira/browse/XMLBEANS-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515072
 ] 

Jacob Danner commented on XMLBEANS-340:
---------------------------------------

Hi Kombi,
will compiling the XSD with scomp -noupa -nopvr *.xsd not work for you until we 
can investigate this further?

I'll look into this further.

In the meantime the offending sections of the XSD are:
<xs:complexType name="TGN">
   <xs:simpleContent>
    <xs:restriction base="dc:SimpleLiteral">
        <xs:simpleType>
          <xs:restriction base="xs:string"/>
        </xs:simpleType>
        <xs:attribute ref="xml:lang" use="prohibited"/>
    </xs:restriction>
   </xs:simpleContent>
  </xs:complexType>

<xs:complexType name="SimpleLiteral">
        <xs:annotation>
        <xs:documentation xml:lang="en">
            This is the default type for all of the DC elements.
            It permits text content only with optional
            xml:lang attribute.
            Text is allowed because mixed="true", but sub-elements
            are disallowed because minOccurs="0" and maxOccurs="0"
            are on the xs:any tag.

            This complexType allows for restriction or extension permitting
            child elements.
        </xs:documentation>
    </xs:annotation>

   <xs:complexContent mixed="true">
    <xs:restriction base="xs:anyType">
     <xs:sequence>
      <xs:any processContents="lax" minOccurs="0" maxOccurs="0"/>
     </xs:sequence>
     <xs:attribute ref="xml:lang" use="optional"/>
    </xs:restriction>
   </xs:complexContent>
  </xs:complexType>

Also, the W3C schema validator had no problems with a HACKHACK XSD I whipped up 
to repro this problem
Here is the output
Schema validating with XSV 2.10-1 of 2005/04/22 13:10:49

    * Target: file:/usr/local/XSV/xsvlog/tmpGJDucGuploaded
         (Real name: foo.xsd)
    * docElt: {http://www.w3.org/2001/XMLSchema}schema
    * Validation was strict, starting with type [Anonymous]
    * The schema(s) used for schema-validation had
        no errors
    * No schema-validity problems were found in the target

http://www.w3.org/2001/03/webdata/xsv








> "derivation-ok-restriction.5.1" failure thrown incorrectly 
> -----------------------------------------------------------
>
>                 Key: XMLBEANS-340
>                 URL: https://issues.apache.org/jira/browse/XMLBEANS-340
>             Project: XMLBeans
>          Issue Type: Bug
>    Affects Versions:  Version 2.3
>         Environment: MacOSX, Java1.5
>            Reporter: kombi
>            Assignee: Jacob Danner
>            Priority: Minor
>
> I downloaded the DublinCore xml schemas and tried to create xmlbeans of them 
> and got several "derivation-ok-restriction.5.1" error messages:
> [xmlbean] schemas/dcterms.xsd:130:3: error: derivation-ok-restriction.5.1: A 
> complex type with a simple content model can only restrict a complex type 
> with simple or mixed content model.
> The problem is here is the line in question:
>   <xs:complexType name="MESH">
>    <xs:simpleContent>
>     <xs:restriction base="dc:SimpleLiteral">
>         <xs:simpleType>
>           <xs:restriction base="xs:string"/>
>         </xs:simpleType>
>         <xs:attribute ref="xml:lang" use="prohibited"/>
>     </xs:restriction>
>    </xs:simpleContent>
>   </xs:complexType>
> Here is the base for the restriction:
>   <xs:complexType name="SimpleLiteral">
>    <xs:complexContent mixed="true">
>     <xs:restriction base="xs:anyType">
>      <xs:sequence>
>       <xs:any processContents="lax" minOccurs="0" maxOccurs="0"/>
>      </xs:sequence>
>      <xs:attribute ref="xml:lang" use="optional"/>
>     </xs:restriction>
>    </xs:complexContent>
>   </xs:complexType>
> As you can see, the complex type with a simple content model is restricting a 
> complex type with mixed content model.
> This seems like an error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to