Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 324174 - [Element Edit Service] Generation of ElementType(s) for a domain
Summary: [Element Edit Service] Generation of ElementType(s) for a domain
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 324966
  Show dependency tree
 
Reported: 2010-09-01 05:54 EDT by Patrick Tessier CLA
Modified: 2013-07-05 10:55 EDT (History)
2 users (show)

See Also:


Attachments
mylyn/context/zip (867 bytes, application/octet-stream)
2010-09-01 05:57 EDT, Patrick Tessier CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Tessier CLA 2010-09-01 05:54:56 EDT
the service creation for a domain can be generated
Comment 1 Patrick Tessier CLA 2010-09-01 05:57:47 EDT
Created attachment 177926 [details]
mylyn/context/zip

impacted plugins
Comment 2 Patrick Tessier CLA 2010-09-01 05:58:01 EDT
the framework generate all element types for UML.
 I have commited a first proposal that can only generated UML element.
 The service creation of UML contains a model that could be used to generated it.
Comment 3 Yann Tanguy CLA 2010-09-10 08:55:58 EDT
The generative tool related to this task consist in a specific metamodel and acceleo based code generation templates.

Its goal is to improve, by modeling and generating, the declaration of a set of IElementTypes and their creation commands.
The metamodel provides an abstraction of these element used in the generation process.

Declaring IElementType for meta classes of a domain model gives the possibility to use the GMF Runtime Extensible Type framework to retrieve edit command for element of the domain model. In case the domain model contains a lot of IElementType to declare this task becomes very tedious. The "DomainContextDodegen" metamodel tries to alleviate the process by automatically creating a declaration node for any metaclass of the domain model (each of these nodes can be manually customized then) and then generating all required Java classes and xml (for plugin.xml file) declarations needed for these element types and related creation commands.

Papyrus requires these element types as its centralized element edit service is currently fully based on the Extensible Type framework offered by GMF (with slight adaptation to ensure it does not interfere with possible use of this framework in diagram code generated by the GMF Tooling.
Comment 4 Yann Tanguy CLA 2010-09-10 09:05:12 EDT
Changes in r2668 :

- "_" added in generated IElementTypes constants, name and hints (e.g. ACCEPT_CALL_ACTION)
- Some useless (or manually defined part) were removed from the code generation process (e.g. Context binding...)
- Handler and ElementType can be generated in different project (and separately)
- The target source  folder can be specified
- Handler generated code was changed (possibility to specify a common super class in the model)
- Generated comment were added in xml generation.
Comment 5 Yann Tanguy CLA 2010-12-14 09:33:27 EST
In r3520:
- Various changes in order to use the same model and generator for SysML elements
Comment 6 Camille Letavernier CLA 2013-07-05 10:55:36 EDT
I close this task