|
Re: Ecore 2 Uml conversion question [message #529639 is a reply to message #529614] |
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
|
|
|
|
Re: Ecore 2 Uml conversion question [message #529844 is a reply to message #529769] |
Tue, 27 April 2010 12:56 |
|
Hi, Mobius,
Sorry, I didn't understand from your first post that the type of the
"properties" attribute wasn't resolved: it wasn't clear to me what the
XML snippet was indicating.
If you have cross-document references, then you need to ensure that all
of your documents are converted to UML in one step, otherwise I suppose
badness will happen. I take it this is what you are doing? If so, then
probably you have a test case for a bug report. There shouldn't be
anything you can specify in a wizard that results in malformed outputs. :-)
Cheers,
Christian
On 27/04/10 03:43 AM, Mobius wrote:
> Christian,
>
> In ecore:
> EType CmisPropertiesType
> in UML:
> Type <Class>
>
> I would expect class CmisPropertiesType in the UML.
>
> Somehow the info is retained, because there is a (wrong, see post)
> reference to the other uml file in the xmi.
>
> I understand I mistook the referce member end for some sort of loopback
> ( which it actualy is!), but still I think the type in uml should be
> CmisPropertiesType.
>
> The link into the 'other uml file' gets lost because the xmi:id of the
> referenced class gets scrambled.
>
> Bug!! or what???
>
> BR,
>
> Mobius
|
|
|
|
Re: Ecore 2 Uml conversion question [message #628413 is a reply to message #628411] |
Tue, 27 April 2010 12:56 |
|
Hi, Mobius,
Sorry, I didn't understand from your first post that the type of the
"properties" attribute wasn't resolved: it wasn't clear to me what the
XML snippet was indicating.
If you have cross-document references, then you need to ensure that all
of your documents are converted to UML in one step, otherwise I suppose
badness will happen. I take it this is what you are doing? If so, then
probably you have a test case for a bug report. There shouldn't be
anything you can specify in a wizard that results in malformed outputs. :-)
Cheers,
Christian
On 27/04/10 03:43 AM, Mobius wrote:
> Christian,
>
> In ecore:
> EType CmisPropertiesType
> in UML:
> Type <Class>
>
> I would expect class CmisPropertiesType in the UML.
>
> Somehow the info is retained, because there is a (wrong, see post)
> reference to the other uml file in the xmi.
>
> I understand I mistook the referce member end for some sort of loopback
> ( which it actualy is!), but still I think the type in uml should be
> CmisPropertiesType.
>
> The link into the 'other uml file' gets lost because the xmi:id of the
> referenced class gets scrambled.
>
> Bug!! or what???
>
> BR,
>
> Mobius
|
|
|
Powered by
FUDForum. Page generated in 0.03581 seconds