I personlly don't see the difference between a Manager and a DAO from the purely bean perspective, as they both as simple beans that are passed to the controllers. I think in my case it would be a bit of an overkill to try to create Managers, as I do not intend to create alternative frontends, other than a Spring MVC frontend.
Regards, Chris alondon wrote: > > I would take a step back and try passing a PictureManager, if you've > implemented one, to the PictureController. I've never passed a DAO > directly to a controller. > > Sorry, > A > > > -----Original Message----- > From: Christian Decker [mailto:[EMAIL PROTECTED] > Sent: Tue 10/28/2008 8:42 PM > To: [email protected] > Subject: RE: [appfuse-user] Accessing DAOs in the controllers > > > Got it, but that didn't fix it :-( > > ---snip--- > public void setPictureDao(PictureDao pDao){ > pictureDao = pDao; > } > ---/snip--- > > alondon wrote: >> >> PictureController needs a setPictureDao(PictureDao pictureDao) method. >> >> -A > -- > View this message in context: > http://www.nabble.com/Accessing-DAOs-in-the-controllers-tp20217953s2369p20219001.html > Sent from the AppFuse - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- View this message in context: http://www.nabble.com/Accessing-DAOs-in-the-controllers-tp20217953s2369p20228945.html Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
