Hi Chad,

thanks for your positive message - good that you are +1 for 4.0! I
continue this discussion on andromda-devel so that the other people
out there can learn what's coming.

Sunday, July 17, 2005, 1:01:44 AM, you wrote:

>>After thinking about Frédéric's statement that ATL will still take
>>some time, I realized that we should not wait but do our homework
>>(which is quite a lot). Until ATL becomes available, we can write
>>model transformations in Java that translate from one metamodel to
>>another (for example, from UML to 3GL). I remember that Pieter van
>>Gorp once said he has a metamodel for Java so we could possibly start
>>using that one as a starting point.
>>

CB> "After thinking about Frédéric's statement that ATL will still
CB> take some time"

CB> What are you referring to....ATL's convergence with QVT or
CB> something else?

No, I am referring to the fact that ATL is still delivered without
source code. So, at the moment, it is not open source, and we should
only use open source software to depend on.

CB> Also, what do you mean with "until ATL becomes available"...its
CB> seems to be available now (at least the binaries), I've been
CB> looking at and playing with it some and it looks like it already
CB> does what we need. I think we should look at using that before we
CB> decide to do the transformations in java (it seems like a lot more
CB> work from what ATL seems to do already).

The work we have to do (as I outlined in the steps) is much more than
just using ATL. I estimate that it will take us quite a while to lay
the foundations for using ATL. They said they will come out with the
sources "at the end of the summer" - this will be early enough for us.
If they should not release in time, however, we should write the
transformations in Java until ATL ships with sources. This will not be
a large amount of work because the transformations themselves will be
quite simple. It's all the other stuff (MOF metamodels, new
metafacades, etc.) that will really take time.

>>All this can and should be done based on MOF, e.g. Netbeans MDR. An
>>old test case in the AndroMDA core once showed how to create model
>>elements in MDR (I do not know whether that one is still part of the
>>code base or has been thrown away in the meantime).
>>  
>>
CB> We already do a small "model transformation" using Java when we add the
CB> default identifiers to entities (so we know how to do it already).

Oh, could you point me to the piece of code? Does it really create
additional nodes in the MOF AST?

>>The main things for us to do would be the following:
>>
>>---Begin vision statement---
>>
>>1) Create a branch for 4.0, enabling us to rearrange things
>>arbitrarily and still be able to ship bug fixes for 3.x.
>>  
>>
CB> Yeah I've been thinking we should start a 4.x branch soon.  I'll go
CB> ahead and create one.

Good! In the meantime, I'll start a COnfluence page to bring a little
more detail into the steps I outlined.

Cheers...
Matthias

---

Matthias Bohlen
"Beratung, die Projekte erfolgreich macht..."

Internet:
   http://www.mbohlen.de/
   [EMAIL PROTECTED]






-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
Andromda-devel mailing list
Andromda-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/andromda-devel

Reply via email to