[ http://jira.andromda.org/browse/CORE-112?page=comments#action_12482 ] Joel Kozikowski commented on CORE-112: --------------------------------------
With this feature, the core should also recognize "null" as a value for any given outlet that means "no code generation." That way, a project can be explicit about "I don't want this code to be generated". Without this support, not declaring the outlet (the current technique used in andromda.xml) would than have the search algorithm fall back on the next most generic outlet and code would be (incorrectly) output there. > Support for hierarchical outlet declarations > -------------------------------------------- > > Key: CORE-112 > URL: http://jira.andromda.org/browse/CORE-112 > Project: AndroMDA Core > Type: Improvement > Reporter: Joel Kozikowski > Assignee: Chad Brandon > > Change the "outlet" attribute in cartridge.xml's <template> declaration to > support a comma separated list, like this: > outlet="server-config, spring-config, project-config" > What the above would mean is: if the outlet "server-config" is declared, > output the file there. If not, try the outlet "spring-config". If its not > declared, output to the "project-config" outlet. If IT is not declared, do > not output the template. > We could then come up with a hierachtical system were the first "outlet" is > specific to the file (so theoritically, each individual template could be > output to a different directory). The next is specific to a sub-system, etc. > with increasingly more generic save locations. > See http://galaxy.andromda.org/forum/viewtopic.php?p=9391#9391 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
