|
| Re: Ecore 2 Uml conversion question [message #628407 is a reply to message #628405] |
Mon, 26 April 2010 15:27  |
|
Hi, Mobius,
What is the type of the "<<eReference>> <property> properties" attribute
in your CreateDocumentType class? I'll bet it is CmisPropertiesType.
The association-owned end is just the non-navigable inverse end required
by a UML association (which must have at least two ends). It has no
correspondent in your Ecore model.
This is all just as it should be.
HTH,
Christian
On 26/04/10 10:39 AM, Mobius wrote:
> Hello there,
>
> I have an ecore model, read from schema.
>
> I have a question about this structure:
> Model
> package Core
> class CmisPropertiesType
> Package Messages
> class CreatedocumentType
> property properties of class CmisPropertiesType
>
> In Ecore this all look well.
> When I convert to UML the property shows up as :
> <<eReference>> <property> properties
> and the association is set to Association <Association>
> A_properties_createDocumentType
>
> In this assoc the member end is set to:
> Member End <<eReference>> <Property> properties, <Property>
> createDocumentType : CreateDocumentType
>
> It seems that I have somehow lost my reference to the CmisPropertiesType
> and end up with a loopback association to CreateDocumentType.
>
> When i look at it in text it looks like:
> <ownedAttribute xmi:id="_JNucdFEREd-RXfSJpGgrjw" name="properties"
> isOrdered="true" aggregation="composite"
> association="_JNuchVEREd-RXfSJpGgrjw">
> <type xmi:type="uml:Class" href="CMIS_Core.uml#_JOBX_lEREd-RXfSJpGgrjw"/>
> </ownedAttribute>
>
> Where this id can't be found in file CMIS_Core.uml (in fact all
> reference-ids to this file begin with _JOB. which is not in the file. (
> the equivalent reference in the exported ecore file can be found in the
> CMIS_Core.xmi file)
>
> Is this expected behaviour?
>
> Best Regards,
>
> Mobius
|
|
|
Powered by
FUDForum. Page generated in 0.03713 seconds
] 
Search
Help
Register
Login
Home
