The Spring Framework has excellent support for JPA, whether you choose to use the JPA templates (similar to JdbcTemplate) or the JPA API directly:
http://static.springframework.org/spring/docs/2.0.x/reference/orm.html#orm-jpa In addition, Rod Johnson, founder of both the Spring Framework and Interface21 wrote the forward to the book "Pro EJB 3: Java Persistence API" calling the Java Persistence API the most important advance in the Java EE 5 platform revision and stating that developers should unite to adopt it. -Scott Quoting Cris J Holdorph <[EMAIL PROTECTED]>: > I've heard the opposite. Especially the Spring community, who normally > would have lots of beefs with JBoss, are more down on JPA. Interface > 21 does not recommend JPA for what it's worth. > > ---- Cris J H > > [EMAIL PROTECTED] wrote: >> You may want to write to the JPA specification instead of the >> Hibernate APIs directly (even if you do end up using Hibernate as >> the backing implementation). >> >> It gives people the flexibility to use what they are comfortable >> with and in the long term doesn't tie you to a specific >> implementation. >> >> http://java.sun.com/javaee/overview/faq/persistence.jsp >> >> -Scott >> >> >> Quoting Cris J Holdorph <[EMAIL PROTECTED]>: >> >>> There are few 'trends' that "most" in the community seem to agree on. >>> >>> Eclipse was the first I noticed in this community. >>> >>> Hibernate and Spring were the second and third (not sure the order). I >>> don't think you'll find much dissension on using Hibernate. >>> >>> But.... If you really wanted to open the door and think about all the >>> reasons why or not, to use Hibernate, there is one downside. >>> >>> RedHat/JBoss and Interface 21 do not get along. I get the impression >>> that some people use iBatis not because they think it's better then >>> Hibernate, but because of the riff here and a desire to use something >>> "other" then Hibernate. >>> >>> Personally, I'd use Hibernate. +1. >>> >>> ---- Cris J H >>> >>> Eric Dalquist wrote: >>>> As I progress with the Pluto 1.1 integration in the trunk I'm >>>> getting closer to the point of needing to write some new DAOs to >>>> persist some portlet domain objects. I would like to propose >>>> using Hibernate 3 for _new_ DAO implementations. Initially this >>>> just provides an easy way to write DAOs for object >>>> persistence, in the very long term we could plan on moving all >>>> DAOs to Hibernate to take advantage of schema creation and >>>> cross-database support. For 3.0 Hibernate would only be used >>>> for new DAOs and all existing data access code would remain as is. >>>> >>>> -Eric >>> -- >>> You are currently subscribed to [email protected] as: >>> [EMAIL PROTECTED] >>> To unsubscribe, change settings or access archives, see >>> http://www.ja-sig.org/wiki/display/JSG/uportal-dev >> >> >> >> > > -- > You are currently subscribed to [email protected] as: > [EMAIL PROTECTED] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
