Oh, and less speaking JPA is a JCP's JSR: so its support and development/improvement will "never" end (at least, in my though). Sun Microsystems may break down (now it owns to Oracle), but somebody will allways been developing the JSRs! ;D
Ice-Man 2009/8/21 Alex Coles <alex.co...@gmail.com> > The biggest advantage has to be using a non-vendor specific API. In > this should mean you can drop in EclipseLink or OpenJPA without too > many issues. I guess for licensing, support reasons you might want to > do this (Apache Roller is an example of an open-source project that > moved from Hibernate to OpenJPA). > > I miss things like the Hibernate Criteria API though. You'll have to > wait until JPA 2.0 for a similar non-vendor-specific API. > > I ported an application to use the JPA API (but still on Hibernate) > and all I can say is it involves careful use of a diff tool! I don't > think the easiest way is to generate a brand-new blank AppFuse > application using the archetype you want, run appfuse:full-source, and > diff away... > > Alex > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net > For additional commands, e-mail: users-h...@appfuse.dev.java.net > >
