Eclipse Community Forums: EMF » XSD2ECORE Many "Types" generated

Help

Home

Home » Modeling » EMF » XSD2ECORE Many "Types" generated(Type generation)

Show: Today's Messages :: Show Polls :: Message Navigator

XSD2ECORE Many "Types" generated [message #686471]

Wed, 22 June 2011 09:49

Bak Attila

Messages: 29
Registered: December 2009

Junior Member

Hi,

I have tested xsd2ecore on maven-v4_0_0.xsd.
The following occurs for elements with :

<xs:complexType>
<xs:sequence>
<xs:element name="dependency" minOccurs="0" maxOccurs="unbounded" type="Dependency"/>
</xs:sequence>
</xs:complexType>

Dependency Type is reused in the xsd however in the ecore file DependencyType2,3 etc will get generated. Exactly as many as there are references in the xsd file.

Why does the xsd2ecore does not recognise that it handles about the same "type" every time and so it should not generate ones...

Any opinion about this?

Thanks
attila

P.S. If you want to see what happens simply import the maven.xsd and you will see what i am talking about...

Report message to a moderator

Re: XSD2ECORE Many "Types" generated [message #687539 is a reply to message #686471]

Wed, 22 June 2011 16:42

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Bak, 
 
Comments below. 
 
 
 
Bak Attila wrote:
<blockquote cite="mid:itsda6$oer$1@news.eclipse.org" type="cite">Hi,
 
 
I have tested xsd2ecore on maven-v4_0_0.xsd.
 
The following occurs for elements with :
 
 
<xs:complexType>
 
 <xs:sequence>
 
 <xs:element name="dependency" minOccurs="0"
maxOccurs="unbounded" type="Dependency"/>
 
 </xs:sequence>
 
</xs:complexType>
 
 
Dependency Type is reused in the xsd however in the ecore file
DependencyType2,3 etc will get generated. Exactly as many as there are
references in the xsd file.
 
</blockquote>
 
I expect additional types to be coming only from anonymous types nested
within the element declaration itself. Certainly I'm not seeing a
problem with the particular scenario you've characterized.
<blockquote cite="mid:itsda6$oer$1@news.eclipse.org" type="cite"> 
Why does the xsd2ecore does not recognise that it handles about the
same "type" every time and so it should not generate ones...
 
 
Any opinion about this?
 
</blockquote>
It doesn't believe such a glaring error could exist... 
<blockquote cite="mid:itsda6$oer$1@news.eclipse.org" type="cite"> 
Thanks
 
attila
 
 
P.S. If you want to see what happens simply import the maven.xsd and
you will see what i am talking about...
 
</blockquote>
Well, as I expected, it's three versions of "DependenciesType"
not "DependencyType" while there is exactly one type called
"Dependency" derived from the one complex type named "Dependency".
Of course the three types come from the three elements named
"dependencies" each with a slightly different (different annotation)
version of a structurally identical complex type definition. 
</body>
</html>

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator