entitymanager

I'm using Hibernate and JPA for a small project. Somehow when trying to obtain an typed Query, the java.lang.AbstractMethodError: org.hibernate.ejb.EntityManagerImpl.createQuery(Ljava/lang/String;Ljava/lang/Class;)Ljavax/persistence/TypedQuery is thrown; org.hibernate.ejb.EntityManagerImpl is from hibernate-entitymanager-3.3.2.GA.jar . This is not okay throwing the above exception: public Account read(Account entity) { EntityManager em = ManagedEntityManagerFactory.getEntityManager(); String jpql = JPQLGenerator.readAccount(); TypedQuery<Account> typedQuery = em.createQuery(jpql, Account.class

Hibernate has a Stateless Version of its Session : Does something similar exist for the JPA EntityManager? I.e. an EntityManager that does not use the first level cache? Not part of the JPA API or spec. Individual implementations may allow disabling the L1 cache. DataNucleus JPA, the one I have used, does allow this From JPA point of view: javax.persistence.EntityManager stands for 1st level cache (persistence context, transactional cache) javax.persistence.EntityManagerFactory stands for 2nd level cache (shared cache) A given persistence provider may implement additional caching layers.

I'm aware that JSR-000220 Enterprise JavaBeans 3.0 Final Release (persistence) spec states: "In general, portable applications should not invoke EntityManager or Query operations, access other entity instances, or modify relationships in a lifecycle callback method." This appears extremely restrictive. We have a situation in which we would like to access the EntityManager from within an EntityListener. Has anyone come across any adverse effects/pitfulls when using the EntityManager from within a Listener on Jboss/Glassfish, or any other application server for that matter? Arthur Ronald F D

I am getting following exception while I try to execute simple JPA 1.0 code. What may be the cause? 5453 DevPQRWDPBSSPersist WARN [P=351601:O=0:CT] openjpa.Enhance - This configuration disallows runtime optimization, but the following listed types were not enhanced at build time or at class load time with a javaagent: "[class com.XYZ.PQR.bss.client.db.data.markerentry, class com.XYZ.PQR.bss.client.db.data.Serviceproduct, class com.XYZ.PQR.bss.client.db.data.Agreementterms, class com.XYZ.PQR.bss.client.db.data.Offeringattribute, class com.XYZ.PQR.bss.client.db.data.marker, class com.XYZ.PQR.bss

I have been searching for this the last few hours maybe some of you can help me. I try to achieve a reload of my mapping info in EntityManagerFactory (or SessionFactory) at runtime in spring The EntityManagerFactory is defined as follows: <bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"> <property name="persistenceXmlLocation" value="persistence.xml" /> <property name="persistenceUnitName" value="JPAService" /> <property name="persistenceProviderClass" value="org.hibernate.ejb.HibernatePersistence"/> <property name="dataSource" ref=

I believe the entity that I wish to delete, is a managed entity. But, regardless, why is merging it then removing it giving me the following error: deleted instance passed to merge Someone said on stackoverflow that merge should be ignored if it is a managed entity. So why is this not being ignored? The way I wish to delete it is like so: TrialUser mergedEntity = em.merge(tu); em.remove(mergedEntity); But this errors, but if I get rid of the first line it seems to work fine. But I want it the other way because that is consistent with the rest of the code. EDIT: @PersistenceContext(unitName =