Hi,
I have a problem with exception like :
org.apache.openjpa.persistence.ArgumentException: No table was given for
persistent type...
...but the table is in the database !
I have copied all jar files and openjpa incubating file to
$GLASSFISH_HOME/domains/domain1/lib/ .
Do You know how can
[
https://issues.apache.org/jira/browse/OPENJPA-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488379
]
Michael Dick commented on OPENJPA-211:
--
Have you started a UserTransaction? That's the only other thing that I
Armad,
This exception doesn't mean the table doesn't exist in the database, it
means that the metadata doesn't define a proper table for this persistence
type. Either the annotations or the xml are not properly defining the table
for this persistence type. It would be good to see the complete
On 4/12/07, Kevin Sutter [EMAIL PROTECTED] wrote:
Armad,
This exception doesn't mean the table doesn't exist in the database, it
means that the metadata doesn't define a proper table for this persistence
type. Either the annotations or the xml are not properly defining the table
for this
Generally in favor of including this performance patch with the
release. Just a few questions:
1. How good is the patch? Has it been put through whatever
extensive Unit Tests tests anyone has?
As others have said, it does pass the OpenJPA test suite, but
unfortunately that isn't saying
hi,
as you know I am switching from EJB2.1 CMP to JPA (OpenJPA). I'd like to
know the preferred way to perform attribute initialisation
of newly created entity instances, e.g.
we initialized our EJB2.1 CMP entity beans with
ejbCreate(String cid, Integer someOtherValue)
{
setabc();
Hi,
Jacek:
Sometimes I do not have access to newsgroup :)
My persistence.xml file :
?xml version=1.0 encoding=UTF-8?
persistence version=1.0 xmlns=http://java.sun.com/xml/ns/persistence;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
Hi Hans,
On Apr 12, 2007, at 8:43 AM, Hans J. Prueller wrote:
hi,
as you know I am switching from EJB2.1 CMP to JPA (OpenJPA). I'd
like to know the preferred way to perform attribute initialisation
of newly created entity instances, e.g. we initialized our EJB2.1
CMP entity beans with
Armad,
Your error seems to have shifted. The original posting indicated that the
exception text was concerning the table metadata:
org.apache.openjpa.persistence.ArgumentException: No table was given for
persistent type...
But, your latest append indicates that the actual database table does
I thought the no-arg constructor had to be public or protected - see
2.1 Requirements on the Entity Class section where this is mentioned.
If that's not the case so much better, but I have been adding a
protected constructor in my entities.
Cheers,
Thomas
Craig L Russell wrote:
Hi Hans,
On
Kevin Sutter wrote:
Armad,
Your error seems to have shifted. The original posting indicated that the
exception text was concerning the table metadata:
org.apache.openjpa.persistence.ArgumentException: No table was given for
persistent type...
But, your latest append indicates that
On 4/12/07, armad [EMAIL PROTECTED] wrote:
First, when I use TopLink or Hibernate everything is ok.
So the entities are good.
Deploy and test process:
I create a .jar file with entities and EJB components, then I deploy it to
the glassfish. Up to this moment everything is ok. But when I run my
[
https://issues.apache.org/jira/browse/OPENJPA-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488488
]
david zhang commented on OPENJPA-211:
-
Even I put openJPA, all the dependant jars in WAS 6.1 plugins directory,
[
https://issues.apache.org/jira/browse/OPENJPA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wisneski reassigned OPENJPA-51:
-
Assignee: David Wisneski
bad sql pushdown, sub select is missing from clause
[
https://issues.apache.org/jira/browse/OPENJPA-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488521
]
Rob Wisniewski commented on OPENJPA-134:
To illustrate the 'eager despite lazy' behavior... here's the
Hello again.
On further searching, I have found that every field in the meta data is
flagged as not being cascade_immediate.
So, during the cascadePersist call, nothing is getting single persisted.
Was I supposed to do something to get these set to 'cascade_immediate'
or is there supposed
Docs seem OK and the examples all run. Looks good to me!
+1 for the release.
On Apr 12, 2007, at 3:20 PM, Michael Dick wrote:
OpenJPA People-
In accordance with the Incubating Releases guidelines at
http://incubator.apache.org/incubation/
Incubation_Policy.html#Releases ,
I've taken a
[
https://issues.apache.org/jira/browse/OPENJPA-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux updated OPENJPA-5:
-
Attachment: OPENJPA-5.patch
The attached patch solves this problem by making all the JDBC
18 matches
Mail list logo
