[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: AW: [jwt-dev] EclipseCon CfP
|
OK guys, Stephane is in, with an interesting use case with SCA, in
addition to Obeo know-how !
Please send your inputs before 12 PM, afterwards I'll submit the talk.
Regards,
Marc
Marc Dutoo a écrit :
Hi Chris (and Stephane)
I respectfully disagree :)
I can't think of a better broad appeal topic at hand. Besides SOA
shared talk, everything is JWT specific, which is fine, but maybe will
have less chances to be okayed - especially if there's a "competing"
shared talk it's in.
Note that the topic won't be the converter, but rather how to answer
the problem of model evolution in Eclipse and EMF - just like at ESE
the topic wasn't our conf-model, but how it answered the model generic
enrichment problem, compared to various other sensible ways of doing it.
Now, I admit it seems there's a lot of software and research on this
topic, but there's been no talk on it at Eclipse Summit or Con yet.
Sure we would have too look into COPE (
http://cope.in.tum.de/pmwiki.php which records EMF changes to ease
model migration), but in order to talk more about AOM we would need at
least this amount of work.
Moreover, Stephane's Obeo are experts about that, so maybe they'd be
interested in a common talk ? Or even other people ?
I can write an abstract right now :
10 minutes talk, 5 minutes demo, 5 minutes debate about the topic with
the audience / shared experience...
"Evolving your metamodel without antagonizing your users" "Painless /
automated metamodel evolution"
* the problem : modeling software evolves, as well as the modeled
domain, and the modelization purpose as well. As years pass, the pain
(of maintaining old models - migrating them - being restricted in
metamodel evolutions that won't break "too much" legacy models) grows
and grows and endlessly piles up...
* solution 1 : modeling practices (subclassing rather than just adding
another type ex. of ExecutableNode, having a version number in the
model, pros and cons of having version-specific namespace, writing
howtos on evolving legacy models in bugzillas...). The user still has
to do everything, so it hurts !
* solution 2 : custom model evolution (java, xsl, further...). Talk
here about what was done before in JWT, simple code that handled by
default namespace changes and evolution, and let execute version
specific code. The user had nothing to do, besides being warned it had
to be converted (screenshot).
* solution 3 : automate use of model transformation software. Here
talk about our ATL model converter, how we only have to add a slightly
changed ATL transformation when the model evolves, how it is truly
painless to the end user & DEMO.
* further : use metamodel evolution records ex. COPE, allow different
strategies, allow automated migration of different referred metamodels
(ex. JWT WE vs conf)
Stephane, do you think it makes sense or not ?
Regards,
Marc
Christian Saad a écrit :
Hi all,
I agree that this is an interesting piece of information that could be
included in a talk but probably not on its own.
Possible presenations:
- Shared SOA talk
- JWT views & aspects: EPC view
- AOM & JWT
- JWT in general (a bit of everything - but with a fancy title!)
Regards,
Chris
-----Ursprüngliche Nachricht-----
Von: jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Florian Lautenbacher
Gesendet: Mittwoch, 9. Dezember 2009 16:17
An: 'Java Workflow Toolbox'
Betreff: AW: [jwt-dev] EclipseCon CfP
Hi Marc,
great idea. Lars Vogel describes that he is a fan of XSLT. In our
approach
we used Java for converting before and now switched to ATL. Probably,
this
is a topic which many people will be concerned at some point of time
and we
could definitely share our experiences in a talk. Although I'm not sure
whether this would fill a complete talk and what would be the advice we
would give the audience in the end.
The question here in addition is, whether we would like to have a joint
talk
with Lars (I don't know him yet) or whether to propose a standalone
talk
describing the pro's and con's of possible converter possibilities.
As mentioned, I won't be able to attend EclipseCon, so this is
something for
Chris (and others) to decide.
Best regards,
Florian
-----Ursprüngliche Nachricht-----
Von: jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx]
Im
Auftrag von Marc Dutoo
Gesendet: Mittwoch, 9. Dezember 2009 15:59
An: Java Workflow Toolbox
Betreff: Re: [jwt-dev] EclipseCon CfP
Hi guys
About EclipseCon :
early bird deadline is tomorrow !
I've got a topic idea with a very broad appeal : the Converter, see
http://www.vogella.de/blog/2009/12/09/evolving-emf-models/comment-page-
1/#co
mment-1094
What do you think about it ?
& see with recent SOA IWG threads
Regards,
Marc
Florian Lautenbacher a écrit :
Hi guys,
this is just a reminder that from today on the EclipseCon 2010 CfP
started [1]. It will be open until 18^th of December, so still quite
some time. But we should not miss this and submit some talks with
great titles (“Aspect-Oriented Modeling” was a good take in my
opinion). As I won’t be able to attend EclipseCon next year, I leave
the discussion about abstracts and what you would like to submit
completely to you.
Best regards,
Florian
[1] http://www.eclipse.org/org/press-
release/20091104_eclipseconcfp.php
---------------------------------------------------------------------
---
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev
