> Now the new requirement: We wanted to have two different Spring > a16t.xml files and two different *.war files so that only those > services were loaded that we wanted to have on each machine. We tried > to solve it with the "modelPackage" option of AndroMDA but this was > a rather indirect, clumsy maintenance intensive hack. > > Could we solve this instead by drawing a UML deployment diagram and > generating the a16t.xml code from it? And: Could we also generate some > metadata that drives the Ant packaging script for the *.war files? > > What do you think? Would be pretty cool! >
yeah that would be a nice feature .. but my feeling is that such changes affect more the build process than it affects the code generation, not sure how we could handle this Chad ? ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Andromda-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-devel
