Thanks, Kalle, all. Looking into Tynamo...
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/DAO-Pattern-tp5714718p5714728.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To
> I am also intrigued by the "generic DAO" concept in the tawus blog, but
> fail to see how to implement, so far.Would be great if this concept,
> if
> I am understanding correctly, could be standardized to pick up directly
> from
> the entities directory for basic CRUD. And similarly pick
On Mon, Jul 23, 2012 at 12:12 PM, netdawg wrote:
> I am also intrigued by the "generic DAO" concept in the tawus blog, but
> fail to see how to implement, so far.Would be great if this concept, if
> I am understanding correctly, could be standardized to pick up directly from
> the entities d
O into Tapestry as
a service. RESTful API can be (should be) application independent, loosely
coupled with the application. Trade off being you lose the ability to
inject, use activation context etc.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/DAO-Pattern-tp
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&qu
.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" packag
, 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 DA
