Alright, Matthias,
lets keep this up one more time :)
As you know, I love XSLT. Anyway, consider some XSLT like
<--- configure this value
from calling the XSLT processor aka stylesheet parameter
Actually, if you would use XSLT templates this should be not
any problem :)
What is XSLT? Is it something to eat or does it hurt? :-)
Yes for sure :-)
I think the best way is to use pure MDR, load the model, traverse the
AST and replace the model element names, then invoke MDR's XmiWriter to
write it back to disk.
I'll try this way. Thanks for the tip!
Cheers,
--
---
>
> Actually, if you would use XSLT templates this should be not
> any problem :)
>
> I hate XSLT :-) If I don't want to use XSLT, what do you
> think is the best way to implement my purpose in AndroMDA *now*?
What is XSLT? Is it something to eat or does it hurt? :-)
I think the best way is
Hi Pieter,
As Krzysztof Czarnecki (author of *the* generative programming book)
describes in
http://www.swen.uwaterloo.ca/%7Ekczarnec/ECE750T7/czarnecki_helsen.pdf,
OptimalJ already has a Java reflection based framework for model
transformations. Wim Bast is working on XMOF, a QVT language ba
Absolutely! A stack of metamodels with transformations in between
stimulates reuse across cartridges. Try to build a cartridge for a
performance pattern for JBoss and WebLogic without using a stepwise
refinement approach... Moreover, at the lowest level of abstraction,
having a metamodel that
Hi Lofi,
> I am not sure what you mean by this kind of transformation, could you
> provide an example please?
A simple example of PIM to PIM transformation would be to translate your
PIM in English language into German language. Normally I model my PIM
in English language because I want to impleme
- snip
Less (or none) transformation between models will surely save time
during code generation. This will save a lot of time for developers
of huge projects. But concerning thos PSMs, if you really model the
PIM, I would think that you should never a
Hi Matthias,
Today I say: Yes, we need true PSMs and AndroMDA will benefit from them!
no doubt anymore ;-) It's true that PSM != UML diagram "view" (what I
said before).
Imagine a UML class with attributes, operations and associations.
Imagine what comes out of the mapping: a Java interface with a
