Dan, Something worth looking at would be: http://static.springsource.org/spring-data/data-jpa/docs/current/reference/html/
There are a few ideas which one may want to borrow, and I believe that a CDI implementation could make things even easier. On Tue, 2011-09-20 at 15:48 -0400, Dan Allen wrote: > On Tue, Sep 20, 2011 at 15:45, Dan Allen <[email protected]> > wrote: > On Tue, Sep 20, 2011 at 15:39, José Rodolfo Freitas > <[email protected]> wrote: > > p.s.: I know that's a really polemic opinion. ;) > > > Let's turn it into requirements then: > > > - developers should be able to develop a CRUD component > without unnecessary boilerplate code > - the developer should be able to easily build on the > out-of-the-box functionality without the scaffolding code > posing unnecessary restrictions > - queries should be declarative (at least in the common cases) > and managed centrally (or partitioned as needed) > > > - the scaffolding code/components should be a natural fit with the CDI > programming model > > > -Dan > > -- > Dan Allen > Principal Software Engineer, Red Hat | Author of Seam in Action > Registered Linux User #231597 > > http://www.google.com/profiles/dan.j.allen#about > http://mojavelinux.com > http://mojavelinux.com/seaminaction > > > _______________________________________________ > seam-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/seam-dev
