On Fri, 11 Feb 2011 07:05:00 -0200, Igor Drobiazko
<[email protected]> wrote:
Hi all,
Hi, guys!
since our last 5.3/5.4 discussion I've been thinking about JPA
integration and came to the conclusion that Tapestry must have a
built-in support for
JPA. Even though I personally still prefer Hibernate, I'm pretty sure
JPA is the future and we need to support it out of the box.
JPA 2 has most (if not all) the features Hibernate has that JPA 1 didn't.
I haven't used JPA yet, but I agree that it's the future.
In the next days I'll add tapestry-jpa module to our SVN. How will this
module differ from Tynamo's module? Well, first of all the Tynamo's
implementation is a copy of tapestry-hibernate module. Implementing
support in Tapestry allows us to reuse code by providing a new module
tapestry-orm.
In addition to that, why don't we create a simple (at least in the
beggining) transaction management package which uses the EJB 3 annotations
and make tapestry-hibernate and tapestry-jpa to use it instead of their
@CommitAfter annotations? This would cover a good part of what is common
for Hibernate and JPA support: transaction management. At first, we could
only support the REQUIRED transaction option (which is the one
@CommitAfter implements) and later we can add more option implementations.
What do you think of it? I just haven't started it myself due to severe
lack of free time. :(
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
