I've been using JPA annotations with Hibernate for a while, but still
using the Hibernate API (SessionFactory, etc.). Those are great, and
I felt right at home with them after using XDoclet to set up
Hibernate mappings for about two years before that.
I'm just getting started using the Persistence API (with Hibernate,
naturally), so it's too early for me to share war stories. So far, so
good, though. While it may sound trivial, that I don't have to
specify the individual annotated classes (or .hbm.xml) is a nice touch.
Venturing slightly (more) off-topic, I recently switched from having
my DAOs extend from Spring's HibernateDaoSupport, and using
HibernateTemplate, to just going directly to the Hibernate API. Or,
now, to the JPA API. I don't benefit from Spring's exception
translation that way, but you know what? I don't think that really
matters (in Hibernate 2, it was helpful, but the exceptions have are
now unchecked). If the applications relied on Spring's DAO
exceptions, this could make it harder to switch from Hibernate to JPA.
Any JPA war stories related to such a switch?
On Sep 14, 2007, at 2:50 PM, Ted Husted wrote:
Since we've had the Struts2 Spring-JPA tutorial up for a while, I was
wondering if many Struts developers were using a Java Persistence API
implementation nowadays, whether the experience has been positive, and
which implementation folks are using (Hibernate, TopLink, OpenJPA).
So, any JPA war stories to tell?
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
