Home/ Questions/Q 272767
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T00:21:14+00:00

One of the most difficult things about understand Spring is that Spring supports multiple

  • 0

One of the most difficult things about understand Spring is that Spring supports multiple approaches to the same problem.

So in my application I using injected EntityManager using the @PersistanceContext annotation, for example:

@Repository
public class JpaDao extends JpaDaoSupport implements Dao {

    @PersistenceContext(unitName = "PersistanceUnit", type = PersistenceContextType.EXTENDED)
    private EntityManager em;

Is this approach compatible with extending JpaDaoSupport (which requires injecting in an EntityManager)? To me it looks like two incompatible approaches to the solving the same problem, but I would like some advice from someone who has more experience with Spring.

If I shouldn’t be extending JpaDaoSupport, how should I build my DAO using the @PersistenceContext approach?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You’re correct that they are two different approaches to the same problem. Which one is “better” is a matter of taste, I think. Using annotations has the benefit of avoiding Spring import dependencies in your code, and even the Spring JavaDoc for JpaDaoSupport suggests using them for new JPA projects. JpaDaoSupport is there to make Spring’s support for JPA equivalent to its support for other ORM strategies (HibernateDaoSupport, JdbcDaoSupport, TopLinkDaoSupport, etc.). In those cases, annotation-based injection isn’t an option.

    • 0