Why don't just use spring to manage EntityManager and transactions? This worked very well for me.
I've just published my "ping-service" project to github so that you can see how JPA/Spring can be implemented in T5 app: http://github.com/dmitrygusev/ping-service I already mentioned this project here on mail list earlier and showed how simple is this to inject EntityManager into my T5 services, just like this: public class JobResultDAOImpl implements JobResultDAO { @PersistenceContext private EntityManager em; @Override public void persistResult(JobResult result) { em.persist(result); } ... and you're done. On Mon, Dec 14, 2009 at 22:21, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > Em Mon, 14 Dec 2009 17:05:03 -0200, Piero Sartini <p...@sartini-its.com> > escreveu: > > > That's what I meant with re-inventing the wheel ;-) >> > > You're right. :) > > > There are already lots of working implementations of JavaEE >> persistence.... but every single web framework needs to build one >> implementation of its own, simulating the specification. Maybe I am >> the only one, but I find this is lost developer power that should be >> used to make the web parts of these frameworks better... >> > > Maybe we could use some light EJB 3.x implementation integrated with > Tapestry-IoC (EJB-defined beans injectable as Tapestry-IoC services). This > is something that will be done eventually. > I've never used EJB, so I don't know what's the necessary effort to do > that. > > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, software architect and developer, Ars Machina Tecnologia da > Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Dmitry Gusev AnjLab Team http://anjlab.com
