That's what I thought ...
Well, in my case, the VO are used both when getting values from the DB to bring them to the UI and when maintaining the state of the UI as session attributes. In the first case, the creation is done by the transformer in the DAO objects, and in the second case, the creation is done by the controller with data comming from the user. So the creation can occur at both end of the stack ... I can duplicate my code (that's really not a lot of it), but I suspect it's not the only time I will use that ... I dont see yet how I can factorize that in a clean way ... Or create a factory for those value objects ? I'll be very happy to hear a bit more about how you would do it ... Thanks ! -- -- Jabber : [EMAIL PROTECTED] (feel free to contact me) _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2594#2594 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
