The code in AndroMDA 2.0.3 goes like this (in the processModelElementWithCartridge method of AndroMDAGenTask):
1. get the element and package names with standard scripthelper 2. for each template: a. get the template's scripthelper b. get the output filename c. do the transformation
So, the solution seems to be putting the first step into the loop, after step (a), so that the names would be determined by the scripthelper supplied by the cartridge.
What do you think about it? Would this cause any trouble
elsewhere (e.g. in other cartridges)?
great!
indeed... it seems that if this would be changed as you proposed the bpm4struts cartridge would be saved;
as for possible consequences I don't see any for the moment, except for the fact that you will need to revert to the default
script helper when none is specified in the descriptor, but that's obvious
maybe the other cartridge developers have some comments on this ?
Wouter.
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Andromda-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-devel
