On tapestry-jdo : I already have a first pass at the implementation(that is, I converted the tynamo-jpa and tynamo-jpa-core to tynamo-jdo and tynamo-jdo-core to use the JDO APIs), but still need to test it out and make sure that everything works as expected. The only thing that didn't transfer over well was the query data grid (or whatever it was called) implementation as JDO doesn't have a type safe criteria API like hibernate or JPA.
I'm not very sure how a common ORM module would work across JPA, Hibernate, and JDO - currently, the mentioned "core" module does deal w/ the API specific classes (e.g. Hibernate with Session, JDO w/ PersistenceManager). Maybe something that straddles Hibernate and JPA would be more feasible as they're much more alike... Cheers, Alex K On Fri, Feb 11, 2011 at 10:02 AM, Kalle Korhonen <[email protected] > wrote: > On Fri, Feb 11, 2011 at 2:24 AM, Thiago H. de Paula Figueiredo > <[email protected]> wrote: > > On Fri, 11 Feb 2011 07:05:00 -0200, Igor Drobiazko > > <[email protected]> wrote: > >> 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. > > Currently, Tynamo offers modules both for JPA1 and JPA2. Igor would > need to work carefully to move the common logic to the orm module, but > certainly it'd be better for code reusability. What would make this > package orm specific? Not absolutely sure it needs to be, I know that > Alex Kotchnev is at least thinking about making a tapestry-jdo module. > > Kalle > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
