1. I'm using tapestry-hibernate; you can put the DAOs in the .services package (well, a sub-package). In the past I used tapestry-spring, in which case the DAOs don't go inside the tapestry project's package.
2. Huh, I had no idea people were using REST on app layer boundaries, rather than just for web services. Where are you going to put your domain logic? Michael On 23 July 2012 14:19, netdawg <net.d...@yahoo.com> wrote: > I have been reading some tapestry DAO resources: > > http://tapestry.apache.org/tapestry5.1/tapestry-hibernate/userguide.html > > http://tawus.wordpress.com/2011/05/28/tapestry-magic-13-generic-data-access-objects/ > http://www.infoq.com/articles/tapestry5-intro/ > > Curious, if there is a standard, established, best-practice, data access > object (DAO) pattern or convention? > > 1. Is there a specific "DAO" package (directory structure for resources)? > Like there is for "entities", "pages", "components", etc? Or is pretty > much > free-form? > 2. I would like the DAOs to be RESTful API...any good examples? Or is it > implicit through the page activation context as mentioned in the infoq > blog? > > Thanks! > > > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/DAO-Pattern-tp5714718.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
