what you would normally do is model a dependency from the controller class to a <<Service>> class, everything is explained here:
in this service you will then call the required code to perform your operations on the persistence layer (as mentioned here: ) just make sure your <<Service>> in turn has a dependency to an <<Entity>> so it has access to the DAO (service.getEntityDao()) and subsequently can call the methods to create/update/find/remove stuff from the DB this only works this way when using Spring, for the other cartridges there are other things you should do, like using one of the generated util classes... -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=828#828 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
