jpa-2.0

I would like to know how to implement temporal tables in JPA 2 with EclipseLink. By temporal I mean tables who define validity period. One problem that I'm facing is that referencing tables can no longer have foreign keys constraints to the referenced tables (temporal tables) because of the nature of the referenced tables which now their primary keys include the validity period. How would I map the relationships of my entities? Would that mean that my entities can no longer have a relationship to those valid-time entities? Should the responsability to initialize those relationships now do by

The DB2-express is throwing an error that seems impossible, when JPA tries to persist an entity: ReportingSQLException: "ITEMID" is not valid in the context where it is used.. INSERT INTO NULLID."DynamicDatabaseTable" ("colname", "rownumber", "value") VALUES (?, ?, ?) [params=?, ?, ?] Since ITEMID is not used in the query above, how can this error be? The ITEMID is an auto-identity-generated column. I have tried executing manually the query and it works OK, so anybody know what's all about? Even after lot of googling, I'm totally clueless here. The database table in DB2 is fine, I have triple

I have an application which processes IQ stanzas via smack (eventbased java library). We now switch from vanilla Tomcat to glassfish 3.1 and i would like to switch to ejb 3.1. @Stateless public class DispatchIQService { private static Logger log = Logger.getLogger(DispatchIQService.class); @PersistenceContext(unitName="hq") private EntityManager em; .... public void process(XMPPConnection connection, IQ rawRequest) { log.debug("Raw Provider IQ: " + rawRequest.toXML()); RawResponse answer = null; try{ StateWrapper state = new StateWrapper(em, connection, rawRequest); // parsing raw xml from

I have an application that uses 2nd level cache on a JBoss AS 7 installation (Infinispan 2nd level cache provider). We have some update JPQL Queries that invalidate the cache- I wonder what will be the effect if we include some native SQL queries in our application. Will the Query cache be invalidated ? Also I remember using the sqlQuery.addSynchronizedQuerySpace("") instruction on Hibernate to prevent cache invalidation for some native SQL queries. Is it possible to do it also with JPA ? Thanks! I came across this question when dealing with the same problem today, so I thought I'd post my

Motivated by this question, I've tried to change the following: @ManyToMany(cascade={CascadeType.REMOVE, CascadeType.MERGE}) private Set<Expression> exps = new LinkedHashSet<Expression>(); to: @ManyToMany(cascade={CascadeType.REMOVE, CascadeType.MERGE}) private LinkedHashSet<Expression> exps = new LinkedHashSet<Expression>(); However, such a move results in: Exception [EclipseLink-1] (Eclipse Persistence Services - 2.1.0.v20100614-r7608): org.eclipse.persistence.exceptions.DescriptorException Exception Description: The attribute [exps] is not declared as type ValueHolderInterface, but its

I am inserting some records in Oracle DB. For the uniqueness, I am using SequenceGenerator. Below is the code: public class XxspPoInLineLocqty implements Serializable { @Id @SequenceGenerator(name = "SequenceLocIdGenerator", sequenceName = "LINE_LOCQTY_JPA_ID_SQ") @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "SequenceLocIdGenerator") @Column(name="LINE_LOCQTY_JPA_ID") private Long lineLocqtyJPAId; //other fields.. } XxspPoInLineLocqty is having @ManyToOne relation with XxspPoInLine. When I am persisting XxspPoInLine entity, I am receiving below error: javax.persistence