[EMAIL PROTECTED] wrote: it should, the implementation will support any modeled class with attributes, no need for the <<ValueObject>> stereotype since this would perhaps generate a VO you don't actually want (end of quote)
why wouldn't I want such VOs? As far as I understand this (VO) pattern it's main purpose is to provide coarse grained access to domain data in a way most useful for client. So I would like to have: 1. a service method: getEntity(): EntityDto called by web controller 2. that EntityDto converted into edit entity form, with form-specific data like field types defined by some tagged values on the dependecy connecting dto to a form 3. after submitting and validating form - form variable in controller should be derived from dto to be able to pass it directly to saveEntity(toSave : entityDto) service method wouldn't that be beautiful? ;-) _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2837#2837 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
