Bug 528788 - UML2EcoreConverter should manage TemplateBinding
Summary: UML2EcoreConverter should manage TemplateBinding
Status: NEW
Alias: None
Product: MDT.UML2
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: UML2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2017-12-14 11:05 EST by Vincent Lorenzo CLA
Modified: 2017-12-30 13:06 EST (History)
0 users

See Also:
Kenn.Hussey: iplog+

Attachments
a draft to support TemplateBinding from UML 2 Ecore (4.88 KB, application/octet-stream)
2017-12-14 11:05 EST, Vincent Lorenzo CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Lorenzo CLA 2017-12-14 11:05:09 EST 
Created attachment 271914 [details]
a draft to support TemplateBinding from UML 2 Ecore

Developing the Expressions Framework in papyrus (org.eclipse.papyrus.infra.emf.expressions), we create a UML Class Diagram, then we generate java code using UML2Ecore tooling. We noticed that the UML Template are not managed by the class UML2EcoreConverter. 

We patch it to answer to our current usecase, but we know it doesn't yet support all the cases defined in the UML Norm. I attach this patch to this bug, but we think it should be considered as a draft and not as a final implementation.
Comment 1 Kenn Hussey CLA 2017-12-15 11:05:46 EST 
Thanks for the contribution, Vincent! I'll take a look and get back to you soon with my feedback.
Comment 2 Kenn Hussey CLA 2017-12-15 13:11:24 EST 
I took a brief look at the patch and have a question. Seeing as the converter already converts templates and their parameters, is the intent of your changes to add support for expanding template bindings, similar to what is already provided by the UMLUtil#expand(...) methods and underlying TemplateExpander class? If so, I wonder whether there's a way to leverage that existing functionality or perhaps simply provide a new converter option to expand template bindings before doing the conversion...