Yes... I've read that, and I agree with it. Basically, if you don't
have to extend an org.springframework.* class in order to get the
functionality you want, than you shouldn't. That being said, I don't
think it's a huge deal if you do. A small preference to the developer
really. I have implemented it how they are describing, without
extending that class, in the current jpa stuff that lives in the sandbox
at: https://appfuse.dev.java.net/svn/appfuse/sandbox/jpa-hibernate-module
André Faria wrote:
*Did you read something about this?
NOTE: JpaTemplate mainly exists as a sibling of JdoTemplate and
HibernateTemplate, to offer the same style for people used to it. For
newly started projects, consider adopting the standard JPA style of
coding data access objects instead, based on a "shared EntityManager"
reference injected via a Spring bean definition or the JPA
PersistenceContext annotation.* (Using Spring's
SharedEntityManagerBean / PersistenceAnnotationBeanPostProcessor, or
using a direct JNDI lookup for an EntityManager on a Java EE 5 server.)
Source:
http://www.springframework.org/docs/api/org/springframework/orm/jpa/JpaTemplate.html
//////
//////
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For
additional commands, e-mail: [EMAIL PROTECTED]
