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 while I do see it as an option, it seems a bit verbose for doing
something that maybe I can do with less code in Tapestry.
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 determining what
Hibernate/JPA entity I am working with) within the ServiceBuilder
implementation. I just don't see how this can be done with
ServiceBuilder.
Is there something obvious I am missing or is the article I mentioned
above the only way it can be done?
Thanks,
Miguel
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
