>The cartridge mechanism provides a way for a user to package up a set of >AndroMDA customizations into a single jar file. The jar can then be >easily distributed and shared with other AndroMDA users. The cartridge >is plugged into AndroMDA simply by adding the jar file to the classpath >of AndroMDA. A typical cartridge will contain a set of custom code >generation templates, supporting java classes, and an XML file that >instructs AndroMDA how to plug these custom pieces into its kernel. >
these supporting Java classes, may they depend on uml14.jar ? or is this reserved for the kernel only ? I was thinking of having some cartridge specific functionality that would not really fit well in the kernel, and alternative would be to put this logic in the templates (what I am doing now) I guess the consequences of doing this might be not easy to spot rightaway ? please note that none of the cartridges depend on andromda-core dependencies (check the cartridge build.xml), I guess there are good reasons... Wouter. __________________________________________________________________ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397 Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Andromda-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-devel
