btw, isn't simply holding values just an extremely simple case of behavior ?
I don't see why you need persistence (entities) to allow an object to exist, not even in enterprise systems; while there's nothing wrong with that all (on the contrary) these Spring fanatics seem to want to cram as much business logic as possible in their POJOs, so they can use them everywhere .. but do you really want to expose all APIs on the same object ? don't get me wrong, I prefer to instantiate as few classes as possible, but sometimes I want to just split responsabilities over different classes, even though they have similar structure for example: suppose you have this kind of entity relation: A --> B --> C --> D; and in the front end you simply like to show the D value for each A instance; if you pass the A entity to the frontend you expose the domain to the presentation layer (which is okay sometimes) but you also now have to perform checks against nullpointer exceptions (suppose C is null), not to mention the performance (the entire tree needs to be serialized into entity classes) -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2613#2613 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
