you will be able to do that, having the <<ValueObject>> stereotype is fine, it's just not mandatory
just consider the case where you want to pass an object that is not a value object .. it still has a few attributes but you don't want a value object generated for it, well this will also be supported by not making the stereotype mandatory I don't see why the stereotype must be there if we have enough with the class attributes -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2839#2839 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
