 13 | ) require an active transaction. In the example above, every Point object is first constructed as ... a managed object (usually by retrieval) and invoke the remove method within the context of an active ... a managed entity object (e.g. by retrieval) and modify it within an active transaction: em |
13 | ) require an active transaction. In the example above, every Point object is first constructed as ... a managed object (usually by retrieval) and invoke the remove method within the context of an active ... a managed entity object (e.g. by retrieval) and modify it within an active transaction: em |
13 | via an EntityManager’s persist method, which must be invoked within an active transaction. On transaction commit ... Entities section. If a managed entity object is modified within an active transaction the change ... the EntityManager’s remove method within an active transaction. The entity object changes its state from |
13 | via an EntityManager’s persist method, which must be invoked within an active transaction. On transaction commit ... Entities section. If a managed entity object is modified within an active transaction the change ... the EntityManager’s remove method within an active transaction. The entity object changes its state from |
13 | . Persistence is set using JPA/JDO annotations (e.g. @Entity, @Id, @Index). Transparent activation (no activation depth) - objects are retrieved from the database automatically by navigating from ... Automatic object versioning (can be injected to a @Version field). Optimistic locking (always active |
13 | . Persistence is set using JPA/JDO annotations (e.g. @Entity, @Id, @Index). Transparent activation (no activation depth) - objects are retrieved from the database automatically by navigating from ... Automatic object versioning (can be injected to a @Version field). Optimistic locking (always active |
13 | /JDO annotations (e.g. @Entity, @Id, @Index). Transparent activation (no activation depth) - objects ... (can be injected to a @Version field). Optimistic locking (always active). Implicit pessimistic |
11 | the content of a database require active transactions. Transactions are managed by an EntityTransaction ... ) must be performed within an active transaction. The EntityTransaction interface represents and manages database |
11 | class or it is a removed entity. A TransactionRequiredException is thrown if there is no active transaction when merge is called because operations that might modify the database require an active |
11 | from inside an active transaction:
Employee employee = em.find(Employee.class, 1);
em ... entity object from within an active transaction. No EntityManager's method is invoked to report |