I've been
playing around with code engineering over the last couple of days. I say playing around since how anybody can actually use EA to do any round trip engineering is currently beyond me!
When using code engineering, I was generating bug reports at the rate of 1 every 4 minutes today (not all day! I had to do other things - my hands were getting RSI (repetitive strain injury) from typing up the reports!) All I do is generate something and then try to reverse it... It almost always doesn't...
I've given up reporting till tomorrow...
Anyhow I've managed to get something going that will do for the present (perhaps until tomorrow).
However, I have one big problem... How do I preserve stereotypes through RTE (round trip engineering).
In order to get around the defective code generator/reverser, I've resorted to using stereotyped overrides on the class declaration and body code generation templates. However, since the stereotype is not passed to the code (that I can see), when I reverse, the stereotype I applied is "
helpfully" removed by the reversal process.
[size=13]
SPARXIANS - this is THINKING 101!!![/size] If you don't propagate the stereotype you don't have the
right to remove the stereotype I've applied.
I'm the blooming modeller, not EA! If (as part of your hard-coded engine), you map certain language structures to predefined stereotypes (such as, enum->enumeration - for C#) then do it, but otherwise leave any other model stereotype alone!
Does anyone know how to get around this problem?It may have occurred to some of you that I'm a bit more pissed off than usual...
You'd be right!!!
It's 11:30pm and I've had a long, very frustrating, day... Off to bed...
Paolo
