I believe he's just saying don't use value objects were you don't need them (which I agree with):
Quote: Transfer objects are a necessary evil in distributed applications (end of quote) . They are necessary in distributed systems (thats why he says "a necessary evil"). If all your application tiers run within the same JVM then a lot of the time you probably don't even need value objects. However as you've seen from Wouter example above, value objects are indeed useful when you want to pass certain datasets to the client (a lot of the time you don't want to pass everything). They also allow you to decouple your client from your your persistence tier (something that may be more important if you have a large project and another team working on the presentation tier for example). Quote: (as opposed to transparently persisted domain objects) (end of quote) I believe he's talking about the entities themselves: (like passing the Hibernate java objects directly to the client for example). All in all, I think it just depends on the system and what you're trying to do when you decide whether or not to use VOs. -- Chad Brandon - [EMAIL PROTECTED] http://www.andromda.org _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2610#2610 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
