Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] [PROVENANCE INTERNET] Re: [PROVENANCE INTERNET] Fixed ids for UML Element type
What not using urine in that case?



Envoyé depuis mon smartphone Samsung Galaxy.


-------- Message d'origine --------
De : Remi Schnekenburger <rschnekenburger@xxxxxxxxxxxxxxxxx>
Date : 04/05/2017 09:41 (GMT+01:00)
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : Re: [mdt-papyrus.dev] [PROVENANCE INTERNET] Re: [PROVENANCE INTERNET] Fixed ids for UML Element type

Hi,

That may be a good idea to facilitate the maintenance, indeed. 

However, what or who would be in charge of such an update? Would it be managed automatically by the element type configuration resource? What would be the algorithm, in case of several existing elements, as for Association specializations? 
If not, and it is processed manually, that will be a nightmare for developers, to ensure that the IDs are unique and updated after each update. There are 240+ metamodelTypes in the uml basic configuration, and much more specialization types in Papyrus configurations (for each representation kind, association specializations, etc.) 

Another drawback is additional work for the project that have already migrated to Oxygen, but this is an issue only for early developers ;) As long as the migration tool for element type configuration is updated.

Cheers,
Rémi

2017-05-04 8:56 GMT+02:00 MAGGI Benoit <Benoit.MAGGI@xxxxxx>:

Hi,

 

That’s the purpose of this mail.

(I personally don’t see any big drawback but I may be missing something)

 

As far as I know, it may be hard to keep ids while editing with a classic EMF editor.

But since these files (uml.elementypes and umldi.elementtypes) shouldn’t change a lot, we should be able to avoid issues

 

/Benoît

De : mdt-papyrus.dev-bounces@eclipse.org [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de GERARD Sebastien
Envoyé : jeudi 4 mai 2017 08:35
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [PROVENANCE INTERNET] Re: [mdt-papyrus.dev] [PROVENANCE INTERNET] Fixed ids for UML Element type

 

It seems to make sense. What are the drawbacks, side effects? 

 

 

 

Envoyé depuis mon smartphone Samsung Galaxy.

 

 

-------- Message d'origine --------

De : MAGGI Benoit <Benoit.MAGGI@xxxxxx>

Date : 04/05/2017 08:31 (GMT+01:00)

À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>

Objet : [PROVENANCE  INTERNET] [mdt-papyrus.dev] Fixed ids for UML Element type

 

Hi everyone,

 

One of the major change in oxygen is the use of references instead of String to “consume” elementtypes.

 

Basically <specializedTypesID>org.eclipse.papyrus.uml.Abstraction</specializedTypesID>

will be replaced by

    <specializedTypes xsi:type="elementtypesconfigurations:MetamodelTypeConfiguration" href="">org.eclipse.papyrus.uml.service.types/model/uml.elementtypesconfigurations#_ScP1oVYCEeS0WsAAtVmToA"/>

in all model ( elementype, palette, new child…)

 

This change was made for good reason but one of the drawback is that we lose human readability of ids

My main concern is the loss of easy Gerrit reviews for use cases such as add an element in palette or new child.

 

I propose to replace uuid (_ScP1oVYCEeS0WsAAtVmToA) by fixed ones (Abstraction)

 

So:

<specializedTypes xsi:type="elementtypesconfigurations:MetamodelTypeConfiguration" href="">org.eclipse.papyrus.uml.service.types/model/uml.elementtypesconfigurations#_ScP1oVYCEeS0WsAAtVmToA"/>

will become

<specializedTypes xsi:type="elementtypesconfigurations:MetamodelTypeConfiguration" href="">org.eclipse.papyrus.uml.service.types/model/uml.elementtypesconfigurations#Abstraction "/>

 

What are your thoughts on the subject?

 

Regards,

Benoît

 

Full example, this

 

  <elementTypeConfigurations xsi:type="elementtypesconfigurations:MetamodelTypeConfiguration" xmi:id="_ScP1oVYCEeS0WsAAtVmToA" identifier="org.eclipse.papyrus.uml.Abstraction" name="UML::Abstraction" hint="UML::Abstraction" editHelperClassName="org.eclipse.papyrus.uml.service.types.helper.DependencyEditHelper">

    <iconEntry xmi:id="_ScP1olYCEeS0WsAAtVmToA" iconPath="/icons/full/obj16/Abstraction.gif" bundleId="org.eclipse.uml2.uml.edit"/>

    <eClass href="http://www.eclipse.org/uml2/5.0.0/UML#//Abstraction"/>

  </elementTypeConfigurations>

 

 

  <elementTypeConfigurations xsi:type="elementtypesconfigurations:SpecializationTypeConfiguration" xmi:id="_eu3zwNx0EeWVxMf7SXAfhg" identifier="org.eclipse.papyrus.umldi.Abstraction_Edge" name="Abstraction Edge" hint="Abstraction_Edge">

    <iconEntry xmi:id="_sWEXUNx2EeWVxMf7SXAfhg" iconPath="/icons/full/obj16/Abstraction.gif" bundleId="org.eclipse.uml2.uml.edit"/>

    <specializedTypes xsi:type="elementtypesconfigurations:MetamodelTypeConfiguration" href="platform:/plugin/org.eclipse.papyrus.uml.service.types/model/uml.elementtypesconfigurations#_ScP1oVYCEeS0WsAAtVmToA"/>

  </elementTypeConfigurations>

 

will become:

 

  <elementTypeConfigurations xsi:type="elementtypesconfigurations:MetamodelTypeConfiguration" xmi:id="Abstraction" identifier="org.eclipse.papyrus.uml.Abstraction" name="UML::Abstraction" hint="UML::Abstraction" editHelperClassName="org.eclipse.papyrus.uml.service.types.helper.DependencyEditHelper">

    <iconEntry xmi:id="_ScP1olYCEeS0WsAAtVmToA" iconPath="/icons/full/obj16/Abstraction.gif" bundleId="org.eclipse.uml2.uml.edit"/>

    <eClass href="http://www.eclipse.org/uml2/5.0.0/UML#//Abstraction"/>

  </elementTypeConfigurations>

 

 

  <elementTypeConfigurations xsi:type="elementtypesconfigurations:SpecializationTypeConfiguration" xmi:id="Abstraction_Edge" identifier="org.eclipse.papyrus.umldi.Abstraction_Edge" name="Abstraction Edge" hint="Abstraction_Edge">

    <iconEntry xmi:id="_sWEXUNx2EeWVxMf7SXAfhg" iconPath="/icons/full/obj16/Abstraction.gif" bundleId="org.eclipse.uml2.uml.edit"/>

    <specializedTypes xsi:type="elementtypesconfigurations:MetamodelTypeConfiguration" href="platform:/plugin/org.eclipse.papyrus.uml.service.types/model/uml.elementtypesconfigurations#Abstraction"/>

  </elementTypeConfigurations>

 

 

 

 

 

 

 


_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev



--
Remi Schnekenburger
Senior Software Architect / General Manager
EclipseSource Paris

Email: rschnekenburger@xxxxxxxxxxxxxxxxx
Web: http://eclipsesource.com/paris 
Phone: +33 1 85 41 08 65
German Phone: +49 89 21 555 30 - 25
Fax: +49 89 21 555 30 - 19
Hangouts: rschnekenburger@xxxxxxxxxxxxxxxxx

EclipseSource France SAS
7 rue de la Croix Martre
91120 Palaiseau

General Manager: Remi Schnekenburger
Registered Office: 7 rue de la Croix Martre, 91120 Palaiseau, France
Commercial Register 824 977 516  R.C.S. EVRY

Back to the top