Re: AW: [Andromda-user] Manipulating the outputPattern

2004-03-02 Thread Lofi Dewanto
Hi Matthias, You will see that the stereotype is now a separate XML element, not an attribute of the template element any more. This allows a template definition to trigger on more than one stereotype which meets your initial requirement about stereotype mapping that you mentioned in your other em

AW: [Andromda-user] Manipulating the outputPattern

2004-03-01 Thread infomail
Hi Lofi, --- Ursprüngliche Nachricht --- Datum: 01.03.2004 07:06 Von: Lofi Dewanto <[EMAIL PROTECTED]> An: [EMAIL PROTECTED] Betreff: Re: [Andromda-user] Manipulating the outputPattern > Hi Matthias, > > yes, this is great, cannot wait to see the newest version of Andr

Re: [Andromda-user] Manipulating the outputPattern

2004-02-29 Thread Lofi Dewanto
Hi Matthias, yes, this is great, cannot wait to see the newest version of AndroMDA! Anyway, I'll go watch your sessions at JAX 2004 (I'll be there as well). Thanks a lot! -- --- Blasius Lofi Dewanto -

Re: [Andromda-user] Manipulating the outputPattern

2004-02-29 Thread Neal Sanche
Matthias Bohlen wrote: Hi Lofi, in the latest CVS version (V3x_MMD branch), I have implemented a new feature: dynamically calculated output file names. It works like this: You calculate your file name inside the Velocity template and assign it to an arbitrary variable, say $myOutputFile: #set ($m

RE: [Andromda-user] Manipulating the outputPattern

2004-02-29 Thread Matthias Bohlen
[EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Lofi Dewanto > Sent: Sunday, February 29, 2004 4:20 PM > To: [EMAIL PROTECTED] > Subject: [Andromda-user] Manipulating the outputPattern > > > Hi Wouter, > > I wonder whether there is a possibility to ma

[Andromda-user] Manipulating the outputPattern

2004-02-29 Thread Lofi Dewanto
Hi Wouter, I wonder whether there is a possibility to manipulate the "outputPattern" within the generation time? I learn your BPM4Struts example at the moment and have some questions ;-): How did you get the outputPattern for the <>? In your template I saw this: So from each ActionState I shoul