Right, this is actually what we are doing.
We have the queries defined in the entity via @NamedQuery (since we
just JPA). Our generic DAO just allows me to specify the name of the
query, set the parameters and get the results back.
Auto-binding is actually what I was looking for, I just have
> >
> >
> > Or you can try to auto-bind them like described here:
> >
> >
> >
> http://killertilapia.blogspot.com/2012/08/autobind-all-tapestry5-services
> > .html
> >
> >
> > On Fri, Aug 31, 2012 at 2:15 AM, Miguel O. Carvajal <
&
here:
>
>
> http://killertilapia.blogspot.com/2012/08/autobind-all-tapestry5-services
> .html
>
>
> On Fri, Aug 31, 2012 at 2:15 AM, Miguel O. Carvajal <
> tapes...@carvajalonline.com> wrote:
>
>> Hey all,
>>
>>
>> I am taking a look again at
O. Carvajal <
tapes...@carvajalonline.com> wrote:
> Hey all,
>
> I am taking a look again at how we have implemented a generic DAO in our
> Tapestry application, since our currently implementation is a bit hackish.
>
> I was looking at the great article over at http://tawus.wordpress.com
Thanks for the reply Thiago.
I see what you mean, but then doing this requires me to create a new
ServiceBuilder instance for each entity. This can get pretty lengthy
with an application that has a lot of entities.
This is why I was looking for a way to automagically create a generic
DAO
On Thu, 30 Aug 2012 19:15:11 -0300, Miguel O. Carvajal
wrote:
Hey all,
Hi!
I saw in the issue 2550
(https://issues.apache.org/jira/browse/TAPESTRY-2550) that
ServiceBuilder was created exactly for this purpose, but since I have no
way of determining the generic type (or other way of
Hey all,
I am taking a look again at how we have implemented a generic DAO in
our Tapestry application, since our currently implementation is a bit
hackish.
I was looking at the great article over at
http://tawus.wordpress.com/2011/05/28/tapestry-magic-13-generic-data-access-objects/
And
