Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9140491
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 17, 20262026-06-17T09:31:23+00:00 2026-06-17T09:31:23+00:00

I am moving a JPA-Hibernate application from a Java EE 6 environment to a

  • 0

I am moving a JPA-Hibernate application from a Java EE 6 environment to a Tomcat 7 one.

The application has several DAO classes making queries on the EntityManager. In the Java EE environment I could just inject it using the @PersistenceContext annotation, and let the container manage the EntityManager. Now that I have to do it manually, I was wondering what is the way to go.

Should the entity manager be unique? If so can it be a static final field, created on startup and that every DAO class uses? Does it have a lifecycle that involves closing it and then re-opening it?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-17T09:31:24+00:00Added an answer on June 17, 2026 at 9:31 am

    Unfortunately, you’ll have to do it manually. The way I usually do it is to define a special class:

    public class EMF {
      private static EntityManagerFactory factory = Persistence.createEntityManagerFactory("name");
    
      public static EntityManager getEntityManager() {
        return factory.createEntityManager();
      }
    }
    

    So, every time you need EntityManager, you have to create it manually. You need to handle transactions as well:

    EntityManager em = EMF.getEntityManager();
    EntityTransaction et = em.getTransaction();
    try {
      MyEntity my = new MyEntity();
      et.begin();
      try {
        em.persist(my);
        et.commit();
      } catch (Exception ex) { 
        if (et.isActive())
          et.rollback();
      }
    } finally {
      em.close();
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm currently moving a (working) app from using EclipseLink to Hibernate JPA, mostly it's
While moving a java file from one plug-in to another plug-in, a dialog box
I'm slowly moving my rails website from a traditional rails round-trip-for-each-view application to one
I'm moving an application from Hibernate to EclipseLink. I have the following named query:
I have been moving a project from JPA to Hibernate native implementation (got outvoted
When moving a site from a staging environment to a production environment, .png image
When moving an application from 32bit to 64bit, where will increased memory usage occur?
Im moving to java from C#, this is my frist try at actually writting
For moving an individual from one branch to another I realize that there are
When moving an object from one collection to another and when cascade is set

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.