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
I believe the reason is that, before anything, the andromda-core code needs to be loaded, with a transformation class instance; when writing the files and determining the names/paths it is this transformation class that is used, and not the one declared inside the cartridge, that one is only used to read from the model and help the templates inside that cartridge
am I right ?
Doroszlai Attila wrote:
Wouter,
a way to achieve this is to be able to specify the
transformation class in the cartridge deployment descriptor, to
enforce its use on that level, instead of overriding a
transformation class on the level of the andromda task
The <template> tag in the cartridge descriptor has an optional attribute called "transformClassname". I think this is exactly the feature you need.
-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
------------------------------------------------------- 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
