After this (most interesting) diversion on the value of Value Object ... Thanks for your explanation. I'll try the utility class idea, which seems to be the cleanest way.
About the utility of VO, in our team (pretty small, 4 developpers) they are pretty usefull. We have a top down area of responsability : each developper is responsible for a feature, from the DB to the UI. Of course, we share some of the entities. Being able to declare the requirements of a feature in term of Value Object means that we dont get in the way of each other. If someone has to modify an entity, as long as the VO are respected, we dont get in the way of one another. That would probably be more tricky if we were dealing directly with the entities. Of course, the problem disapear once the data model (entities) are stabilized ... -- -- Jabber : [EMAIL PROTECTED] (feel free to contact me) _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2616#2616 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
