About injection

41-50 of 50Refresh
Issue
1

objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active'

; one can't inject with @EJB in a loop. One can also make a build depend on various states in previous
Forum
1

On initialisation of lists: impact on migration from EclipseLink to ObjectDB

I would like to draw the attention of those assessing migration from EclipseLink ORM to ObjectDB to a significant difference in the initialization of persistent lists, namely that EclipseLink injects a List implementation into the List field to be initialise it during EntityManager.persist(). So in
Forum
1

Optimistic locking: prevent version increment on entity collection attribute

injection and Guice persist and should get one EntityManager per request. Also, please note that in the web
Forum
1

Out of memory

.annotation.InjectionMetadata - Processing injected method of bean 'inspirationIndex
Forum
1

Pessimistic Lock Timeouts setting

creates one processor bean with an injected stateful EJB which holds an instance of Entity Manager
Forum
1

Remove an entity which attributes were changed - OptimisticLockException

. You can do that easily by adding a version field to the entity class, so the version number will be injected
Forum
1

Sorting problem

arguments without recompilation) and also for security sake (to avoid SQL injection when the parameter
Forum
1

system exception occurred during an invocation on EJB GuestDao

: same problem (see below). How can I verify if the EntityManager has been successfully injected
Forum
1

Update is ignored by ObjectDB

managers. I think that this problem is related to EJB injection behavior of ObjectDB
Forum
1

Visibility of changes in Transaction is not visible to a JPA QL Query

= bean.findItem((int)which); //bean merely passes call to singleton with injected EntityManager