1

Currently we're creating a single EntityManager per request in our web app. We're wanting to create a transaction at the beginning of the request and close it at the end to get automatic transaction support throughout the entire request.

Has anyone tried this? and will this introduce concurrency issues or is should we just wrap all of our update code in a separate transaction?

Note we're using JPA 1.0

Vineet Reynolds
  • 76,006
  • 17
  • 150
  • 174
joekarl
  • 2,118
  • 14
  • 23
  • 1
    What server (specifically, what version) is this running on? Is there a reason you can't just have the `EntityManager` injected into your EJBs using `@PersistenceContext`? – Matt Ball Dec 12 '10 at 04:40

1 Answers1

1

For simple apps, this is enough (one transaction per request). But for more complex scenarios you will need to use transactions on more granular level.

In principle I always wrap my update transactions as needed.

Anyway your approach doesn't prevent you to open a new transaction in the middle of the request if needed. So it is OK by me.

And something about the possible concurrency issues... If you can foresee issues, address them, otherwise I wouldn't worry too much about it. Keep it simple and don't get caught up in premature optimizations

Bojan Milenkoski
  • 501
  • 5
  • 13