Hi,
I'm facing a ClassCastException in the context of a PersistentCollection.
It sound like exactly the behavior described here :
http://issues.apache.org/jira/browse/OPENJPA-1020
This bug look like fix but without any OpenJPA fix version.
Any news ?
I'm using a 1.2.2 snapshot from september.
Hi Mohammad,
I don't think we can set a system property by using persistence.xml and even if
we could, that would affect your entire app server anyways. System properties
affect the whole JVM even if set during runtime.
The Oracle doc you mentioned [1] suggests that you can use
I'm building a REST-based app using CXF and OpenJPA 1.2.1. The app
works fine, but I've noticed that the first request to the app after
startup takes quite a while, and most of the time is spent on the first
JPA request. Following requests, even for different objects and
classes, goes much
-Original Message-
From: KARR, DAVID (ATTCINW)
Sent: Tuesday, December 29, 2009 9:05 AM
To: users@openjpa.apache.org
Subject: XML overrides annotations, except when it doesn't
Both the JPA spec and the OpenJPA doc implies that if I have
annotations
on a field and a definition for
-Original Message-
From: KARR, DAVID (ATTCINW)
Sent: Wednesday, December 30, 2009 10:58 AM
To: users@openjpa.apache.org
Subject: RE: XML overrides annotations, except when it doesn't
-Original Message-
From: KARR, DAVID (ATTCINW)
Sent: Tuesday, December 29, 2009 9:05
I am using openjpa 1.2.0 and derby db. I am getting this error message once
in a while. does anybody know why I am getting this.
Is there something wrong with the derby db table or something?
org.apache.derby.client.am.SqlException: The data in this BLOB or CLOB is no
longer available. The
I am using openjpa 1.2.0 and derby db. I am getting this error message once in
a while. does anybody know why I am getting this.
Is there something wrong with the derby db table or something?
org.apache.derby.client.am.SqlException:
The data in this BLOB or CLOB is no longer available. The
For JPA 2.0 (OpenJPA trunk), the map key does not need to be a field in the
target entity. For example, please see the test case in
org.apache.openjpa.persistence.jdbc.maps.*.
- Original Message
From: KARR, DAVID (ATTCINW) dk0...@att.com
To: users@openjpa.apache.org
Sent: Tue,
-Original Message-
From: Fay Wang [mailto:fyw...@yahoo.com]
Sent: Wednesday, December 30, 2009 1:47 PM
To: users@openjpa.apache.org
Subject: Re: How to implement a map where the key is in the join
table,
not in the target table?
For JPA 2.0 (OpenJPA trunk), the map key does not
I've been assembling an app using OpenJPA 1.2.1 for a few weeks now.
I've just come to the conclusion that the app is going to require
reading data from more than one database datasource. One user schema
has most of the tables, but another user has some other tables. There
are some references
10 matches
Mail list logo