Wouter, > ah yes, that's true, but I remember trying it. It was not working for > some reason, I believe it was that the method for generation of > file/package names is done on the level of the <andromda> tag, although > we specify the transformation class in the descriptors, the file names > would be generated depending on the default transformation class of the > core package > > am I right ?
You are right in that the output filename would not be determined by the helper specified on the template tag. The output filename is not determined (directly) by the scripthelper at all, but by the TemplateConfiguration class, as a second look at the code revealed. :) The scripthelper only provides the names of the model element and the package. 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)? -Attila ------------------------------------------------------- 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
