Hi All,
While trying to generate the EMF model for the updated .dbs schema
following things were found.
1. <xs:element name="call-query"> appear in <result>,<operation>,<resource>
tag definitions with the same definition while previous schema clearly
define
it separately and referenced on relevant positions well.
Problem :- When generating ecore model it defines CallQueryType1 ,
CallQueryType2 ext..
2. In most of the cases content based restrictions are not there
for an example In previous schema
<xs:element
name="property" maxOccurs="unbounded" minOccurs="1">
<xs:complexType ecore:name="ConfigurationProperty">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="name" type="xs:string" use="required" />
</xs:extension>
<xs:simpleContent>
</xs:complexType>
</xs:element>
but in updated schema
<xs:element name="property"
maxOccurs="unbounded" minOccurs="1" />
Problem :- In the ecore model, the class reffered to those
configurations are not defined with data types with true meaning. Because
of not well defined content types
EMF defines "AnySimpleType" but it is not acceptable
when we are in the EMF context.
Please have a look.
Thanks,
Kalpa.
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
