jpa-2.0

I'm trying to build an implementation agnostic maven module which relies on JPA2. Unfortunately, the only Maven JPA dependency is JPA1 based, and consequently, I cannot use EntityManager.detach() method as that is a JPA2 option only. Ideally, I'd love to be able to specify my javax.persistence dependency in my Pom, and require the app/container to supply the JPA2 implementation. Unfortunately, I cannot find any such dependency. Is my only choice at this point to declare hibernate-jpa-2.0-api 1.0.0.FINAL as a provided dependency? Gene De Lisa The Hibernate JPA 2 classes (javax.persistence...)

With JPA 2 Criteria Join method I can do the following: //Join Example (default inner join) int age = 25; CriteriaBuilder cb = entityManager.getCriteriaBuilder(); CriteriaQuery<Team> c = cb.createQuery(Team.class); Root<Team> t = c.from(Team.class); Join<Team, Player> p = t.join(Team_.players); c.select(t).where(cb.equal(p.get(Player_.age), age)); TypedQuery<Team> q = entityManager.createQuery(c); List<Team> result = q.getResultList(); How can I do the same with fetch method, I expected that Fetch interface had get method for path navigation but it doesn't: //Fetch Join Example int age = 25;

I'm currently learning the new Java EE 6 component models and am confused with the latest dependency injection mechanism. So here are my questions: 1) What is the difference between @Inject and @EJB 2) If I have a simple POJO that contains another POJOs (which one of them is the DAO code), what would be the better choice: @Inject or @EJB? Can I mix @Inject and @EJB? An example would be: ClassA implements InterfaceA and has an instance of ClassA_Adaptor ClassA_Adaptor implements InterfaceAB and has an instance of ClassB ClassB implements InterfaceB and has an instance of ClassB_Adaptor and an

I found some instructions how to configure pure hibernate to use EHCache. But I can't find any instructions how to configure JPA2.0 EntityManager to use cache. Hibernate 3.5.2 is my JPA2.0 provider. edit// Is @Cacheable(true) enough for entity? Or should I use @org.hibernate.annotations.Cache to configure the entity? Pascal Thivent I found some instructions how to configure pure hibernate to use EHCache. But I can't find any instructions how to configure JPA2.0 EntityManager to use cache. Hibernate 3.5.2 is my JPA2.0 provider. The way you configure the L2 cache provider with JPA is similar is

I'm trying to create a criteria to retrieve some objects from 3 tables (Associate, Update and Detail). A Detail has reference to Associate and Update, and an Update has reference to a list of Details. My objective is to retrieve a list of Updates that has at least a Detail with null value in a specified field, given an Associate id. In JPQL was easy to do but the client said that this must be coded with criteria. My JPQL was: public List<Update> getUpdates(long associateId) { TypedQuery<Update> query = em.createQuery("select distinct u from Update u, Detail dt, Associate a " + "where dt.update

I'm using Spring Boot 1.2.5 with JPA2 to annotate entities (and hibernate as underlaying JPA implementation). I wanted to use second level cache in that setup, so entities were annotated with @javax.persistence.Cacheable I also added following in application.properties: spring.jpa.properties.hibernate.cache.use_second_level_cache=true spring.jpa.properties.hibernate.cache.use_query_cache=true spring.jpa.properties.hibernate.cache.region.factory_class=org.hibernate.cache.ehcache.EhCacheRegionFactory During bootup hibernate complained about lack of EhCacheRegionFactory so I also added this to

...without actually reading and parsing the persistence.xml I can retrieve the name of the persistence unit of an EntityManager using the properties of it's factory . I can retrieve the available datasources using the jboss-as-controller-client . But I have found no API that would give me the datasource of a particular EntityManager . A String with a name would be enough. Thank you I am working with Hibernate 4.0.1.Final over JPA 2 on a JBoss 7.1.1.Final. EDIT: and I would like to avoid straying from JPA to Hibernate APIs if possible. EDIT : Augusto's solution worked, I have some notes on