here's an example:
notice how the RentalService has a dependency to both entities, if you take a look at the service's base class you'll see the DAO accessors: http://galaxy.andromda.org/docs/andromda-spring-cartridge/resources/howto/org/andromda/test/3/RentalServiceBase.java this class is the parent of the class in which you will add your implementation for entities you can have the same behavior: any dependency from A --> B will generate a getBDao() in A's DAO, not in the entitiy itself makes sense ? this kind of stuff is never generated in any xxxImpl.java class, instead we want to be able to regenerate this without touching your manually edited files, so it always goes into an ancestor class -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1825#1825 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
