Bug 570401 - Camel Case Names option results in semantically important base_Class property name changing to baseClass
Summary: Camel Case Names option results in semantically important base_Class property...
Status: NEW
Alias: None
Product: MDT.UML2
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: UML2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-15 20:20 EST by Deniz Eren CLA
Modified: 2021-01-16 02:14 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Deniz Eren CLA 2021-01-15 20:20:43 EST
Issue found regarding EMF feature "EMF Generator Model" when setting "UML Import" Option "Camel Case Names" to "Process" configuration.

Issue if that UML property such as "base_Class" gets beautified to be "baseClass" with the "_" character being removed when the "Camel Case Names" options is set to "Process" configuration.

This is an issue because the exact name "base_Class" has semantic importance to UML models. This beautification that removes the "_" character also ultimately results in the failure of the Papyrus static profile as discussed in detail in this Papyrus forum:
https://help.eclipse.org/2020-12/topic/org.eclipse.papyrus.uml.diagram.profile.doc/target/generated-eclipse-help/users/generatingStaticProfiles.html?cp=73_0_1_8_5

Please note that this is not only or specifically applicable to "base_Class" property; it also applies to other UML metamodel stereotype applications, for example "base_Abstraction", "base_Association", "base_Classifier", etc...
Comment 1 Ed Willink CLA 2021-01-16 02:14:26 EST
This is a problem in the beautification offered by the UML 'added value'. EMF is more consistent.