Thanks Martin, that does solve the main task at hand.
Going a step further, I also am hoping to figure out a way to implement a stereotype in a manner that provides me tagged values that can all be set to true initially, but could allow me to set some to false. Let's say I need the 4 audit fields described in the example above for all classes, except a logging table - where I only need dateAdded and addedBy. I was thinking that a set of 4 tagged values could all be set to true and then for the logging entity, i could set the updatedBy/dateUpdated values to false. In which case, the cartridge would not implement the properties that map to that "template". I'm probably incorrectly using terminology here (a recent noob). For now, your solution will work and gives me what I need. BTW, have you looked at the Enterprise Patterns and MDA book by Arlow/Neustadt? Covers the patterns you are using. I found it to be a good Amazon find. Thank you again, -matt _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=455#455 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402&alloc_id=16135&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
