You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xmlbeans.apache.org by "Radu Preotiuc-Pietro (JIRA)" <xm...@xml.apache.org> on 2005/12/21 02:10:40 UTC

[jira] Resolved: (XMLBEANS-239) Complex type with complexContent which extends a base type with simpleContent causes scomp failure

     [ http://issues.apache.org/jira/browse/XMLBEANS-239?page=all ]
     
Radu Preotiuc-Pietro resolved XMLBEANS-239:
-------------------------------------------

    Resolution: Fixed

SVN revision 358168

> Complex type with complexContent which extends a base type with simpleContent causes scomp failure
> --------------------------------------------------------------------------------------------------
>
>          Key: XMLBEANS-239
>          URL: http://issues.apache.org/jira/browse/XMLBEANS-239
>      Project: XMLBeans
>         Type: Bug
>   Components: Compiler
>     Versions: Version 2.1
>  Environment: All
>     Reporter: Lawrence Jones
>     Assignee: Lawrence Jones
>     Priority: Minor
>      Fix For: TBD
>  Attachments: test_bmecat.xsd, xmlbeans239.patch2
>
> If you have a schema with the setup as follows:
>     <xsd:complexType>
>         <xsd:complexContent>
>             <xsd:extension base="baseType"> ...
> Then the baseType referenced must (by rule 1 http://www.w3.org/TR/xmlschema-1/#src-ct) be a complex type. However the spec does _not_ specify that the baseType must itself have complexContent. It appears that the spec allows simpleContent. However XmlBeans as it stands will fail specifying that a complex type _with complex content_ must be provided. Example error message is below:
> bmecat_2005.xsd:3681:5: error: src-ct.1: The specified base type 'typeMLSTRING00050@http://www.bmecat.org/bmecat/2005fd' must be a complex type with complex content.
> If we remove the check at StscComplexTypeResolver line 529 that checks for simpleContent (without removing the check for simpleType) the checkintest appears to work and we get files generated which compile correctly. I will attach a patch which does that and updates the error message.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org