2010 06 22 omg - obeo

1
Eclipse / OMG
Symposium
2010/06/22 - Minneapolis, USA
Etienne JULIOT
etienne.juliot@obeo.fr
Acceleo:
implementation of Mof-to-Text Language
When a de facto standard could become
a reference implementation

© Copyright 2009 Obeo made available under the EPL v1.0 | 27 October, 2009
Migrating an OSS Project to Eclip
From Acceleo.org to Eclipse Modeli
 Eclipse Strategic Member
 12 commiters on Eclipse Modeling Project
(most of them related to OMG spec):
 M2T : Acceleo
 M2M : ATL
 EMF : EMF Build, EMF Compare, EEF
 GMF
 OCL
 Amalgamation …

Our job:
 Domain Specific
Modeling
 Viewpoint approach
Migration
Reverse engineering
 Training and Expertise
 Taylor made

Summary
 From Acceleo.org to Eclipse Acceleo
 Acceleo and MTL standard
 Others contribs in the OMG scope

Once upon a time

 Built on Eclipse: State of art of tooling
 Pragmatism: Create a dedicated tool and keep using
the others
 Magic inside: Easy to start with
Acceleo original spirit

 Events, Conferences, Press , University
 Lively forum and mailling lists, roadmap, history, team page
 Planet Acceleo
 Acceleo Modules Repository
 JavaEE (Struts, Hibernate ..)
 C# (Nhibernate)
 Python, Zope, PHP
 C
 Java
 Ecosystem : Capgemini, Makina Corpus, Lyria, Proxiad …
 +10 000 downloads / month
Building the community

What's next?

In the meantime
 OMG released the MOF Model To Text Language Specification
 The Acceleo core team is convinced it's the way to go

Why Eclipse Foundation?
 Visibility
 Easier integration with other projects
 OMG's reference implementations are in Eclipse
 Obeo's involvement in Eclipse Modeling
 We loved the « Best Open Source Eclipse-Based
Developer Tool » award !

The challenge
 Keeping the spirit while moving to the OMG standard
 Keeping the project's user base
 Playing well : « The Eclipse Way »

Acceleo's new implementation aka : Eclipse Acceleo
3.0
 Starting from scratch
 State of the Art ++ Tooling
 Usable everywhere: JAR, OSGi, Eclipse RCP or IDE

Main Features
 Editors
 Advanced completion
 validation, quick fixes, show references, open declaration...
 Views to manage overrides , patterns
 Eclipse Integration
 Debugger, Profiler
 Module UI: create automatically a Popup Action to Generate
 Init wizards from examples (bottom-up approach)
 Architecture
 Java API, generator pluginization
 Standalone core

Acceleo Syntax – Model to Text Language (MTL)

Which strategy for a
« standard AND pragmatic »
implementation?

OMG Specification
Helios : complete support
excepted Macros and code
explicit syntax
 Compliance Level
 Standard evolution at the OMG
 Interactions with the OMG are slooooooow
 STD versus Non-STD library for blocker features:
 Text indent, encoding management
 Syntax enhancement to simplify user's life
 Services to reuse EMF and Java features

Collaboration plan
STD
v1.0
NONSTD
STD
v1.1
NONSTD

We want to be explicit for end users

Few words on OCL
 OCL is a Constraint Language, not a Request Language
 A template based syntax MUST BE short and easily readable
 « Normal users » don't like to write "collect, select, reject, oclAsType"
everywhere
 OCL contains a lot of features that are of no use whatsoever for code
generation; namely everything that's "constraint specific"
 But, with several enhancement, it's fine
 Our strategy:
 Using an extensible approach for the model request language
 Re-use Eclipse OCL Plug-in to insure interoperability, and extend it

MTL/OCL enhancements
 Filter:
 Acceleo 2:
<%sequence["Type"]%>
 Pur OCL:
[sequence->select(oclIsKindOf(Type)).oclAsType(Type)/]
 Acceleo 3:
[sequence->filter(Type)]

 Model browsing:
 Acceleo 2:
<%for (ownedElement["ControlFlow"].nSort("name")%>
 Pur OCL:
[for (cf:ControlFlow |c.ownedElement->select(a|a.oclIsKindOf(ControlFlow))->sortedBy(e:
Element | e.oclAsType(ControlFlow).name))]
 Acceleo 3: implicit iterator
[for (c.ownedElement->select(oclIsKindOf(ControlFlow))-
>sortedBy(oclAsType(ControlFlow).name))]
 Acceleo 3: inference
[for (c.ownedElement->filter(ControlFlow)->sortedBy(name))]
- Package
|-- Activity
|-- ControlFlow1
|-- ControlFlow2
|-- ControlFlow3

 Xpath like services:
 Acceleo 2:
<%x.followingSibling%>
 Pur OCL:
[x.eContainer().eContents()->subSequence(x.eContainer().eContents()-
>indexOf(self), x.eContainer().eContents()->size())->excluding(self)/]
 Acceleo 3:
[x.followingSiblings()]

 Operators on Collections:
 Acceleo 2:
<%list1 – list2%> <%list1 + list2%> <%list1 || list2%> <%list1 &&
list2%>
 Pur OCL:
complex combinaisons of « set / orderedset / union /
symmetricDifference »
 Acceleo 3:
[list1->asSet() - list2->asSet()/] [list.addAll(list)] [list.removeAll(list)]

 String:
 Acceleo 2:
<%"ab" + "cd" + "ef"%>
 Pur OCL:
["ab".concat("bc").concat("ef")]
 Acceleo 3:
["ab" + "cd" + "ef"]

But code generation without tooling is like
word processing with notepad ....

Completion

 Protected Areas (STD)
 JMerge (Non-OMG STD but Eclipse STD)
User Code

 Dynamic contributions / Template Aspects
Advanced Eclipse Features

Quickfix

Refactoring

Rapid text replacement

Generation Pattern

Debugger

Profiler

 M2M and M2T interoperability (with ATL and QVT-O)
Advanced Eclipse Features
 Java extensions

Problems with OMG
 5 bugs signaled (http://www.omg.org/issues/mtt-rtf.open.html)
 No ACK
 No answer
 Ask to list Acceleo as an MTL implementation on the OMG website:
still waiting after 1 year
 No contact point and no status publicly available
 We would like to contribute, but it's not easy …
 But: spec is good, users are happy, syntax is powerful
and still simple, and we have now interoperability through engines

Acceleo 3 community
 Lead : Jonathan Musset, OBEO
 Committers
 Wim Bast
 Cedric Brun, OBEO
 Laurent Goubet, OBEO
 Arjan Kok
 Yvan Lussaud, OBEO
 Users (some)
 Integrators (Atos Origin, CS, Proxiad, Capgemini, ...)
 Industrial (Pole Emploi, Thales, …)
 Editors and Individuals
 Others projects (EEF, TopCased, ...)

But Acceleo isn't alone!

ATL
module Families2Persons;
create OUT : Persons from IN : Families;
-- helpers declaration {
-- ...
-- } helpers declaration
rule Member2Male {
from
s : Families!Member (not s.isFemale())
to
t : Persons!Male (
fullName <- s.firstName + ' ' + s.familyName
)
}
rule Member2Female {
from
s : Families!Member (s.isFemale())
to
t : Persons!Female (
fullName <- s.firstName + ' ' + s.familyName
)
}
 Model transformation engine
 Inside Eclipse M2M project
 Declarative and Imperative
approach
 Based on OCL and close to QVT
 Editor, Debugger, Profiler,
Refactoring, ...
 QVTo or QVTd  ATLvm

Traceability
 With M2T and M2M
 No intrusion in input or output
 Nothing to configure in rules or
templates
 Desynchronisation detection
(precision: character or element)
 Traceability across
transformations chains
 Engine in OpenSource projects

EMF Compare
 Differency detection
 2 ways and 3 ways mode
 Merge
 Extensible engine
 XMI and XML support
 Intermediate metamodel for
Match, Diff and Patches

GMF  Domain Specific Modeling
 3 implementations
 API engine (GMF Runtime)
 Generative engine (GMT Tool)
 Interpretive engine (Obeo Designer)
 New approach: Viewpoint
 Lack of separation between graphical
diagrams and semantic
(ex: sequence diagram on non-UML
models)
 Lack of standardisation of viewpoint
(Notation)

Thank you
 http://www.eclipse.org/acceleo
 http://www.obeo.fr

2010 06 22 omg - obeo

Recomendados

Recomendados

Más contenido relacionado

Similar a 2010 06 22 omg - obeo

Similar a 2010 06 22 omg - obeo (20)

Más de Etienne Juliot

Más de Etienne Juliot (15)

2010 06 22 omg - obeo