[
https://issues.apache.org/jira/browse/XMLBEANS-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758189#action_12758189
]
Luis Barragan commented on XMLBEANS-377:
----------------------------------------
Is there any update on this issue?
I am getting the same error message "SchemaTypeLoaderException: Simple type
does not have a recognized variety" but in my case it seems to be related to a
substitution group.
<xsd:complexType name="IdentifierType">
<xsd:complexContent>
<xsd:extension base="qq:IdentifierType">
<xsd:attribute name="mandatory"
type="xsd:boolean"/>
<xsd:attribute name="order" type="xsd:int"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
"qq:IdentifierType" refers to a type defined in another schema.
So I get the error while getting a new instance of IdenfierType:
IdentifierType.Factory.newInstance();
> exception in thread "main" org.apache.xmlbeans.SchemaTypeLoaderException:
> Simple type does not have a recognized variety
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: XMLBEANS-377
> URL: https://issues.apache.org/jira/browse/XMLBEANS-377
> Project: XMLBeans
> Issue Type: Bug
> Components: Tools
> Affects Versions: TBD
> Environment: Ubuntu 8.0.4, jdk1.5.14, XMLBeans 2.4.0
> Reporter: Matt Bucknam
>
> I'm having the same issue as with XMLBEANS-356. I can provide more
> information if necessary but hope that something similar to what fixed that
> issue will fix this too. The schema fragment that does not work is:
> <xs:complexType name="AngleMeasureType">
> <xs:annotation>
> <xs:documentation>An angle measurement, with an
> associated error bound. The units on the error bound are assumed to be the
> same as those on the measurement.</xs:documentation>
> </xs:annotation>
> <xs:complexContent>
> <xs:extension base="xxxxx:DecimalType">
> <xs:attribute name="angleUOM"
> type="xxxxx:AngleUOMType">
> <xs:annotation>
> <xs:documentation>A unit of
> measurement assigned to this angle.</xs:documentation>
> </xs:annotation>
> </xs:attribute>
> </xs:extension>
> </xs:complexContent>
> </xs:complexType>
> Similar to the suggested workaround given in XMLBEANS-356, if I change the
> xs:complexContent to xs:simpleContent and recompile the schema, I can use it
> just fine. But, also similar to XMLBEANS-356, I am a consumer of the schema
> and am not able to easily change it. If a sample xsd and java program to
> duplicate the problem are necessary or more information please let me know
> and I'll try to provide. The fragment is part of a very large complex set of
> schemas and is proprietary so I am trying to be diligent in what I post.
> Thanks.
--
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]
