XSD -> Java -> UML

[Kurt T Stam <kstam@redhat.com>]

Hi guys,

As part of the work I am doing for S-RAMP-1, I have used the xsds to 
generate Java and then I used the Java to generate UML.

It turns out that in my UMLs a lot of the 'Navigability' relationships 
are lost. For example look at the core model and look the relation 
between DerivedArtifactType and DocumentArtifactType.

The reason why this is lost is that in the xsd the relation is mapped 
using a reference to 'target':

<!--
        Relationship target artifact's UUID. Used by all types of
        relationships
    -->
<xsd:complexType name="target">
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:anyAttribute namespace="##any" />
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>

This allows you to set a UUID of the document you are referencing in the 
String value (as well as additional attributes), but it breaks the 
'referenced object' relationship.

The conclusion must be that the UMLs in the document do no map to the 
xsds. It looks like this level of indirection was introduced on purpose 
after the creation of the UMLs.

1. It'd be nice to understand why this was introduced, if done 
intentionally.
2. It'd also be nice to understand where the attributes on Target can be 
used for.

I guess we can discuss all of this next week.

Cheers,

-Kurt

p.s. The Java objects can be found here: 
http://github.com/Guvnor/guvnor-sramp/tree/master/guvnor-sramp-api

Attachment: s-ramp-fig1-core-model.png
Description: PNG image

Attachment: s-ramp-fig2-soa-model.png
Description: PNG image

Attachment: s-ramp-fig4-service-model.png
Description: PNG image

Attachment: s-ramp-fig5-policy-model.png
Description: PNG image

Attachment: s-ramp-fig6-xsd-model.png
Description: PNG image

Attachment: s-ramp-fig8-wsdl-model.png
Description: PNG image

Attachment: s-ramp-fig9-wsdl-model.png
Description: PNG image

Attachment: s-ramp-fig10-soap-wsdl-model.png
Description: PNG image