Association of a WSDL type element witits XSD type

[Guillaume]

Hi,

I've got a couple of WSDL files that I imported in EA (v9.3).
I also use an XML Schema file (.xsd) that I imported in the same EA  package as my WSDL files.

Opening a WSDL package in EA & its "XSDSchema" Type package, I have my XSD element which type is defined in the XML Schema file.
If I open this element, I get the correct name of the Type with the name of the XSD but it's not associated with the corresponding UML class in EA (resulting from the XSD import)
EA will let me manually choose the right UML class in the model but I was wondering a workaround to make EA automatically do this.

As it currently works I have no option to obtain traceability when importing my WSDL file (provided I've already imported my XSD)

Here is an example :

WSDL file content :
<xs:element name="Something" type="xsdfile1:Something_Type"/>

XSD file content
<xs:complexType name="Something_Type">
<xs:sequence>
....
</xs:sequence>
</xs:complexType>

>> both files are imported (XSD then WSDL)

Thanks in advance for any help

[Guillaume]

Having looked further into this issue, I think that EA doesn't support XSD that are shared by several WSDLs.

I created a WSDL namespace pkg and an XSDSchema pkg.
In the WSDL \ XSDschema Types, I created a new element and specified as its type an element from the external XSD. EA creates an inheritance between the 2 classes.

When generating the WSDL and XSD files, and importing them back into a new EAP, this inheritance is lost.

This seems to be a feature request for EA unless I've missed something out.

thanks

[tjs]

Is this conclusion accurate?  I have not found a way to import an xsd into the wsdl via sparx ea.