About EntityManagerFactory

11-20 of 200Refresh
JPA Doc
65

getPersistenceUnitUtil()

Method javax.persistence.EntityManagerFactory PersistenceUnitUtil getPersistenceUnitUtil() Return interface providing access to utility methods for the persistence unit. Returns: PersistenceUnitUtil interface Throws: IllegalStateException - if the entity manager factory has been closed Since: JPA 2.0
JPA Doc
65

getProperties()

Method javax.persistence.EntityManagerFactory Map getProperties() Get the properties and associated values that are in effect for the entity manager factory. Changing the contents of the map does not change the configuration in effect. Returns: properties Throws
JPA Doc
65

isOpen()

Method javax.persistence.EntityManagerFactory boolean isOpen() Indicates whether the factory is open. Returns true until the factory has been closed. Returns: boolean indicating whether the factory is open Since: JPA 1.0
Manual
62

Shared (L2) Entity Cache

by the EntityManagerFactory and shared by all its EntityManager objects. the broader scope ... to the EntityManager's L1 cache and the EntityManagerFactory's L2 cache, which are managed ... is wider, since they exist per database and are shared by all the EntityManagerFactory and EntityManager
Manual
39

Chapter 3 - Using JPA

Explains how to store, retrieve, update and delete entity objects using JPA.
JPA Doc
39

JPA Reference (JavaDoc)

Java/JPA API Reference (based on the JPA 3 JavaDoc)
Manual
27

Obtaining a JPA Database Connection

content also require an EntityTransaction instance. Obtaining an EntityManagerFactory Obtaining ... of EntityManagerFactory that represents the relevant database and then we can use that factory instance ... to be able to generate an EntityManagerFactory. But when using ObjectDB you can either define a standard
Forum
23

EntityManagerFactory Fails To Swtich Over To Slave When Master Is Unavailable

; public static void main(String[] args) {   EntityManagerFactory emf = null;   EntityManager em = null ... ) {   EntityManagerFactory emf = null;   EntityManager em = null;   try {    emf = Persistence ... . I see the following stack trace. Notice EntityManagerFactory switched over to the slave
Forum
22

High memory consumption even after close() of EntityManagerFactory

could not be released. Not even after the EntityManagerFactory closed. We created a small test ... ) on EntityManagerFactory close.   The optimization of memory usage was very effective. The test ... released (if active) on EntityManagerFactory close. However, there are other structures
Forum
22

Objectdb EntityManagerFactory problem

. You can close each EntityManagerFactory by using the close method. By the way, creating an EntityManagerFactory is relatively slow. It is usually better to use one EntityManagerFactory