Hi Lofi, <quote> All this should possibly be done in AndroMDA 3.x because it changes the API of the generated code significantly and would require users to change their code.
Upps... I'm doing this in the lastest version 2.x. Should I move to the 3.x first? Could you please explain this? </quote> people are using the EJB, Hibernate and Struts cartridges from AndroMDA V2.x and would be very irritated if we gave them cartridges that generate completely different APIs than before. Therefor, you should do this in V3.x, but that one is unstable at the moment because I port it to a new concept called metamodel decorators. I think the best thing is that you write your cartridges for AndroMDA 2.x and port them to use metamodel decorators when they will be finished (January or so). Cheers... Matthias --- Matthias Bohlen "Consulting that helps project teams to succeed..." http://www.mbohlen.de/ ------------------------------------------------------- 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-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
