Hi Wouter, thanks a lot for your insight!
I'm doing the Enhydra/Barracuda/XMLC stuffs at the moment,
and would like to have a similar way with your BPM4Struts.
Only the stereotype's name would be a little bit different,
therefore we really need the stereotype mapping names as I
asked before ;-).
A
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
-
Hi Lofi,
The cartridge currently is undergoing some major changes, I realized it
is better to be a little more verbose in the UML model because it allows
the cartridge to produce cleaner and more stable Struts code; I put a
notice on the wiki page saying it is not a good idea to rely too much on
t
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
Hi Wouter,
sorry to disturb you again. Seeing the newest docu from
the Wiki page, it seems that you changed <>
to describe a Class instead of ActionState, is this true?
So, I don't need to describe <> for my ActionState
any longer? Instead you use "@andromda.struts.action.state" tag?
Is this becau
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 ($myOutputFile = ${class.s
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
