Hi all,

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.

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.

So, the plan is:

- add tapestry-orm module which will contain the functionality from
tapestry-hibernate-core. This module will be use by both tapestry-hibernat
and tapestry-jpa. For backward compatibility reasons we can't just rename
the packages org.apache.tapestry5.hibernate to org.apache.tapestry5.orm, but
need to copy the classes.
- Deprecating tapestry-hibernate-core in 5.3, removing it in 5.4.
- Refactoring tapestry-hibernate to use tapestry-orm

-- 
Best regards,

Igor Drobiazko
http://tapestry5.de

Reply via email to