Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "VIATRA2/UML2EJB"
(New page: == Description == The aim of this model transformation is to generate a skeleton of Enterprise Java Beans (EJB3) from UML class diagrams. The related metamodels and transformations will b...) |
m (Added outdated page notice) |
||
Line 1: | Line 1: | ||
+ | == Outdated page == | ||
+ | This page contains obsolete information about the VPM based VIATRA2 and preserved for archive purposes only.<br /> | ||
+ | The currently maintained wiki is available at http://wiki.eclipse.org/VIATRA | ||
+ | |||
+ | __NOTOC__ | ||
+ | |||
== Description == | == Description == | ||
Latest revision as of 04:14, 30 April 2015
Outdated page
This page contains obsolete information about the VPM based VIATRA2 and preserved for archive purposes only.
The currently maintained wiki is available at http://wiki.eclipse.org/VIATRA
Description
The aim of this model transformation is to generate a skeleton of Enterprise Java Beans (EJB3) from UML class diagrams. The related metamodels and transformations will be developed in a step-by-step manner to present some VIATRA design patterns and best practices. As a result, this transformation serves as a complex tutorial.
This code generation task will be carried out by two separate transformations:
- UML-to-EJB: A first transformation will derive an EJB3 model from UML class diagrams
- EJB-to-Java: A second transformation will generate Java code with EJB3 annotations from the EJB3 model
Separating this code generation task into two steps is already the first design pattern, which provides
- more freedom in designing the more complex UML2EJB step (as we do not need to deal with Java serialization at the same time)
- a straightforward model transformation for the actual code generation.