Now that I've got these DAOs accessible I've noticed the generated toCollection methods have void return. Maybe its just down to my own coding style but its got me wondering about normal practice for use of those methods and implications for change of entity attributes which are persisted by hibernate.
eg. in particular for an EntityDAOImpl I'm coding a toEntityVO() implementation and in there want to populate a collection of subordinate VOs (eg. call them SubEntityVO) Inside the EntityDAOImpl I can do: getSubEntityDAO().toSubEntityVOCollection(Collection c) but say I passed c as entity.getSubEntities() I'd expect that would convert the SubEntity instances within the Collection thats already related to the entity itself. I could then retrieve the collection from there no trouble but I wonder what effect doing that has on the entity in hibernate if it needs be persisted or accessed again at some later point. Doesn't seem like good practice? If so wouldn't it be better for the toSubEntityVOCollection to be generated to return a new Collection ? I realise I'm probably missing something here, otherwise you'd be doing otherwise but I just can't see why. :? -- Audere est Facere _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1889#1889 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
