jpa-2.0

I need to use JPA 2.0 (with the EclipseLink implementation). The problem is that I also need to deploy this app in a WebLogic 10.3.6 server, which implements the Java EE 5 specification, and so, it is not required to support JPA 2. I know that there are patches that can be used to add support for JPA 2.0 in this version , but the sysadmin doesn't want to change anything in the server at all I tried adding the javax.persistence-2.1.0.jar file to my war thinking that my app would just use this file instead of the one provided by WebLogic. Does this make any sense? Is there a way to achieve this

I'd like to apply JPA in the following (simplified) database: NODE AUTHORITY ----- ---------- idNode int idAuthorities int nameNode varchar(50) person varchar(255) idAuthorities int rank int PRIMARY KEY (idNode) PRIMARY KEY (idAuthorities, rank) FOREIGN KEY (idAuthorites) So one node can have multiple authorities and one authority can be referenced by multiple nodes. And I wanted my classes to look like: @Entity @Table(name="NODE") public class Node { private Integer id; private String nameNode; private Set<Authority> authorities; // ... getter and setter normaly annoted for "id" and "nameNode

I have two eclipse Java EE 6 projects packaged in a WAR-file using maven 3. Now they should share JPA entities in a 3rd project among them, since they both use the same database. When doing the research for my question, I found some hints mentioning for example a reference in a persistence.xml to a common jar, but I wasn't successful to make it work. So specifically asked: 1) Does the project, containing the common entities, has a persistence.xml file? If so, how does it differ from the one in the other projects? 2) How exactly are the commonly used entities referenced in the two projects? Do

I need a JPQL for the MySQL query: SELECT * FROM table1 t1 INNER JOIN table2 t2 ON t1.id = t2.table1.id INNER JOIN (SELECT * FROM table1 t3 INNER JOIN table2 t4 ON t3.id = t4.table1.id WHERE t3.name = 'xxx') subTable ON t1.number = subTable.number WHERE t1.number = '5' AND id = '3' Your query seems quite pathological, perhaps say what result you are trying to query, and include your object model. In general, JPQL does not support sub-selects in the from clause, so your query is not directly convertable to JPQL. You can always just execute it as a JPA native SQL query, since you seem to be