jpa-2.0

I'm trying to run a query that checks if some conditions are true and returns a simple boolean result as output. What makes it slightly tricky is that one of the conditions is to test for whether no results are returned for a set of criteria. I'm currently using JPA-2.0 with hibernate as my provider, backed by MySQL. I have gotten an example query working fine in MySQL, but when trying to get it running in JPQL it flops. The MySQL query looks a bit like this: Select exists(Select statement with criteria) or not exists(Select statement with criteria); I also got the same output using CASE, but

I'm using QueryDSL with JPA2 for some time, and it's the most powerful combination for ORM I know. JPA Criteria API is a disaster. With QueryDSL I've forgotten about JPQL too. I'd like to use QueryDSL with Play! Everything looks very good in Play except those inline parts of JPQL as strings. It reminds me of CakePHP... I'd like to have refactoring-proof querying language in Play (and some other things :) ). QueryDSL usage would be straightforward. It needs EntityManager only. But QueryDSL has this APT class generator (just like the one from Hibernate for citeria API). Does anyone managed to

I'm using Hibernate 3.3.1 and am following along in modelling this sample table structure , but I'm having trouble creating a join table with extra attributes. It's the many-to-many relationship between the Order and Product table. The join table is the Order Detail table. I followed the approach mentioned here . Now I have the entities @Entity @Table(name = "Orders") public class Order { @OneToMany(mappedBy="order") private List<OrderDetail> orderItems; } and @Entity @Table(name="PRODUCTS") public class Product { @OneToMany(mappedBy="product") private List<OrderDetail> orderItems; } and

I'm using hibernate-entitymanager 3.6.4.Final and h2 database 1.3.155 I'm using the H2Dialect. I'm having trouble filtering records by elements in an @ElementCollection. Here is my entity @Entity public class Item { @Id @GeneratedValue(strategy = GenerationType.AUTO) @MapKeyColumn(name="name", length=50) @Column(name="value", length=100) protected Map<String, String> attributes; /* etc. */ } Here is my query : Item item = em.createQuery("FROM Item i JOIN i.attributes a WHERE KEY(a)='myAttrName'").getSingleResult(); Here is the error message : 4971 [main] WARN org.hibernate.util

Good Day all , I am having this problem since many days now , I was able to successfully deploy JPA2.0 appliaction on weblogic 10.3.3 , the application can run select queries using JPA. But when I try to run a create or update information on the same table I get below exception [code] java.lang.ClassCastException: org.eclipse.persistence.jpa.PersistenceProvider cannot be cast to javax.persistence.spi.PersistenceProvider [/code] This is very strange because in my persistence.xml I have provided hibernate as JPA provider , the persistence unit defined is like below [code] <persistence-unit name=

I am using JSF2 with Pure JPA2. But the problem is with entityManager, @PersistenceContext private EntityManager entityManager; Here entityManager is not getting injected and always null. Can some one please help me what is wrong in my code. Here is my configuration. User.java @Entity @Table(name="USER") public class User { private int id; private String name; private String surname; @Id @SequenceGenerator(name="user_id_seq_gen", sequenceName="USER_ID_GEN_SEQ", allocationSize=1) @GeneratedValue(strategy=GenerationType.SEQUENCE, generator="user_id_seq_gen") @Column(name="ID", unique = true,

There is the possibility to disable the @OneToMany relationship join table with the @JoinColumn annotation. The default is a join table. What are the advantages and disadvantages for a production system for example? When should I use a join table and when not? Thank you. By default @OneToMany will create a join table only if you'll use unidirectional relationship . In other words, if you have Employee and Project entities and the Employee entity is defined as follows (assume there is no orm.xml entries for these entities) : @Entity public class Employee { // ... @OneToMany Set<Project>