ObjectDB Database Search
1-25 of 25 resultsjakarta.persistence.PersistenceContexts.value
Jakarta Persistence (JPA) Method in jakarta.persistence. PersistenceContexts PersistenceContext [] value (Required) One or more PersistenceContext annotations. Since: Jakarta Persistence (JPA) 1.0
|
|
jakarta.persistence.PersistenceContext.properties
Jakarta Persistence (JPA) Method in jakarta.persistence. PersistenceContext PersistenceProperty[] properties (Optional) Properties for the container or persistence provider. Vendor specific properties may be included in this set of properties. Properties that are not recognized by a vendor
|
|
jakarta.persistence.PersistenceContext.name
Jakarta Persistence (JPA) Method in jakarta.persistence. PersistenceContext String name (Optional) The name by which the entity manager is to be accessed in the environment referencing context; not needed when dependency injection is used. Default: "" Since: Jakarta Persistence (JPA) 1.0
|
|
jakarta.persistence.PersistenceContext.unitName
Jakarta Persistence (JPA) Method in jakarta.persistence. PersistenceContext String unitName (Optional) The name of the persistence unit as defined in the persistence.xml file. If the unitName element is specified, the persistence unit for the entity manager that is accessible in JNDI
|
|
jakarta.persistence.PersistenceContext.type
Jakarta Persistence (JPA) Method in jakarta.persistence. PersistenceContext PersistenceContextType type (Optional) Specifies whether a transaction-scoped persistence context or an extended persistence context is to be used. Default: PersistenceContextType.TRANSACTION Since: Jakarta Persistence (JPA) 1.0
|
|
jakarta.persistence.PersistenceContext.synchronization
Jakarta Persistence (JPA) Method in jakarta.persistence. PersistenceContext SynchronizationType synchronization (Optional) Specifies whether the persistence context is always automatically synchronized with the current transaction or whether the persistence context must be explicitly joined
|
|
jakarta.persistence.PersistenceContexts.class
No JavaDoc Info for jakarta.persistence. PersistenceContexts /class
|
|
JPA Container Injection Annotations
). A container annotation for declaring multiple @ PersistenceContext definitions on a single class ... within @ PersistenceContext or @PersistenceUnit to specify configuration properties for the injected resource.
|
|
jakarta.persistence.EntityManager
EntityManager may be obtained by dependency injection, using PersistenceContext . // inject the container-managed entity manager @ PersistenceContext (unitName="orderMgt") EntityManager entityManager ... accepts LockOption s. See Also: Query TypedQuery CriteriaQuery PersistenceContext
|
|
Step 3: Define an EJB Session Bean
.persistence. PersistenceContext ; import javax.persistence.TypedQuery; @Stateless public class GuestDao { // Injected database connection: @ PersistenceContext private EntityManager em; // Stores a new guest ... (because it is annotated with the @ PersistenceContext annotation). Handles transactions automatically using
|
|
Step 3: Define a Spring DAO Component
; import javax.persistence.EntityManager; import javax.persistence. PersistenceContext ; import javax ... connection: @ PersistenceContext private EntityManager em; // Stores a new guest: @Transactional public ... the em field (because it is annotated with the @ PersistenceContext annotation). Handles
|
|
Step 3: Define a Spring DAO Component
.List; import javax.persistence.EntityManager; import javax.persistence. PersistenceContext ; import ... connection: @ PersistenceContext private EntityManager em; // Stores a new guest: @Transactional public ... the em field (because it is annotated with the @ PersistenceContext annotation). Handles
|
|
jakarta.persistence.EntityManagerFactory
may be obtained by dependency injection, using PersistenceContext , and the application need not interact
|
|
ObjectDB within a resource adapter module and Java EE Connector Architecture
adapter module can't be used, is there another @ PersistenceContext -friendly strategy for separating ... turn leverage the persistence.xml, which is automatically used via: @ PersistenceContext private ... (which can also be an ObjectDB database url) in the unitName parameter of @ PersistenceContext
|
|
Object DB vs EclipseLink/TopLink: Unloaded relationships in detached entities
is declared using the PersistenceContext annotation or the persistence-context-ref deployment ... for the entity manager is defaulted or defined as PersistenceContext - Type.TRANSACTION. A new persistence ... . The dependency on the extended persistence context is declared by means of the PersistenceContext
|
|
Persist not working when ObjectDB and another db is used in the same application (through spring) with different tx managers
; Persistence code @ PersistenceContext (unitName = "testPU") private EntityManager em; @ PersistenceContext (unitName = "mysqlPU") private EntityManager em1; @Transactional
|
|
Cannot save or update entity on Spring App
: @ PersistenceContext private EntityManager em; // Stores a new guest: @Transactional public Language persist ... LanguageRepository extends DefaultRepository{ // Injected database connection: @ PersistenceContext private
|
|
Problem on JPA Merge Entity.
ErgoDaoJpa implements IErgoDao { @ PersistenceContext private EntityManager entityManager; public void
|
|
UserException - Object User#2 belongs to another EntityManager
@Stateless bean TradesC#findTradeByClient(User u). ### UserC and TradesC have their own @ PersistenceContext
|
|
Undeployment of an remote Glassfish application locks objectdb log file
System: Netbeans 7.1 Oracle Glassfish 3.1.2 ObjectDB 2.3.7_04 Senario: Create a simple WebApplication with a "hello world" web service interface in Netbeans. Add objectDB test code to the web service: @WebService(serviceName = "NewWebService") public class NewWebService { @ PersistenceContext
|
|
Visibility of changes in Transaction is not visible to a JPA QL Query
{ @ PersistenceContext (unitName = "Experiment8objPU" ) EntityManager emInj; /**  
|
|
How force always recreate database on redeployment.
an EntityManager from the container using @ PersistenceContext . I can then obtain the related
|
|
Spring MVC Errors
that query is using a closed EntityManager although I use that @Autowired and @ PersistenceContext
|
|
An entityManager.flush() with many entities is not possible
The following exception occures if we call entityManager.flush() where the corresponding JPA PersistenceContext has many entities and relations. What is the reason for the exception ... PersistenceContext is too complex. [ObjectDB 2.6.0_01] javax.persistence.PersistenceException
|
|
Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct)
; @ PersistenceContext private EntityManager em; public List findElements ... ; @ PersistenceContext (type=PersistenceContextType.EXTENDED) // change 2 private
|