Hi Yu Wang,
You need to tell OpenJPA that you're not using the Connection any more
by calling close(). See this Example 4.4 in the user's manual:
import java.sql.*;
import org.apache.openjpa.persistence.*;
... OpenJPAEntityManager kem = OpenJPAPersistence.cast(em);
Connection conn =
Since it looks like we still have some performance and cleanup work
before we create a 2.0.0 release, several of us were chatting off-line
and decided that a 2.0.0-beta instead of a 2.0.0-M4 would be more
appropriate, given we're passing the TCK and have made significant
progress towards a 2.0.0
OpenJPA 1.2.2 is now available from
http://openjpa.apache.org/downloads.htmland from the ibiblio maven
repository. Version 1.2.2 is a bugfix release
which includes 24 notatble bug fixes and 9 improvements.
The complete list of issues resolved can be found in the release notes at
-Original Message-
From: Miłosz Tylenda [mailto:mtyle...@o2.pl]
Sent: Wednesday, December 30, 2009 7:03 AM
To: users@openjpa.apache.org
Subject: Re: Best way to prime OpenJPA before first request?
I'm building a REST-based app using CXF and OpenJPA 1.2.1. The app
works fine,
Rick is the expert here, but the 1.2.2 release contains an improvement to do
the metadata repository initialization up front. This has shown to greatly
improve both performance and scalability. I believe you kickstart this
activity by using the following property...
property
-Original Message-
From: Kevin Sutter [mailto:kwsut...@gmail.com]
Sent: Thursday, January 21, 2010 12:41 PM
To: users@openjpa.apache.org
Cc: Rick Curtis
Subject: Re: Best way to prime OpenJPA before first request?
Rick is the expert here, but the 1.2.2 release contains an
Kevin - Close, but no cigar. NoLock=true isn't valid.
I'll get the docs fully updated today or tomorrow.
--
Thanks,
Rick
On Thu, Jan 21, 2010 at 2:41 PM, Kevin Sutter kwsut...@gmail.com wrote:
Rick is the expert here, but the 1.2.2 release contains an improvement to
do the metadata
After replacing 1.2.1 with 1.2.2 and turning on the metadata preload, I
got a nonsensical column that is not compatible error. I then tried
removing the preload setting, and it's fine. I set it back, and it
failed again, so it's repeatable.
The relevant part of the stack trace is this (some
Are you listing your persistent types in the p.xml file?
On Thu, Jan 21, 2010 at 3:43 PM, KARR, DAVID (ATTCINW) dk0...@att.comwrote:
After replacing 1.2.1 with 1.2.2 and turning on the metadata preload, I
got a nonsensical column that is not compatible error. I then tried
removing the
To whom it may concern:
german magazin 'Java Spektrum' 1/2010, page 32, published an article about
experiences from
porting from Hibernate to OpenJPA.
greeting
dieter von holten
Craig,
I have tested it. It's cool!
The db connection will be returned into pool and I can reuse the
JPAEntityManager!
Thanks again.
Regards,
Yu Wang
On Fri, Jan 22, 2010 at 9:57 AM, wang yu wangy...@gmail.com wrote:
Craig:
Thank you for your quick response.
If I close it, the connection
Hi,
On Jan 21, 2010, at 7:23 PM, Russell Collins wrote:
While the initial thought is that the equals() method would work,
the specification for Set requires a compareTo method be present by
implementing the Comparable interface.
This is not my understanding. Set requires only hashCode and
Thanks for using OpenJPA and the users alias. Good luck.
Craig
On Jan 21, 2010, at 7:35 PM, wang yu wrote:
Craig,
I have tested it. It's cool!
The db connection will be returned into pool and I can reuse the
JPAEntityManager!
Thanks again.
Regards,
Yu Wang
On Fri, Jan 22, 2010 at 9:57 AM,
Hi,
I am experiencing problems with an EAR deployed onto Websphere 7. The EAR
contains a web module and an ejb 3 module that uses openjpa 2 for
persistence.
More than half the time after redeploying the EAR, for each EJB3 class, I
would get the following kind of error the first time I invoke
Thanks for your response and time ...
Yeah I think for now I will go with the nullifying the columns at entity
level .
--
View this message in context:
http://n2.nabble.com/How-to-specifiy-Cascase-None-for-OneToMany-tp4426059p4438679.html
Sent from the OpenJPA Users mailing list archive
Hi Milosz,
I am using DB2 9.5 and Microsoft SQL Server 2005.
Thank you for creating the JIRA issue, I would be very interested in future
support for collection valued paths as I am currently falling back on native
queries for such paths.
Stella
On Fri, Jan 15, 2010 at 8:35 PM, Milosz Tylenda
Hi all,
I still got his problem and can't seem to resolve it so I'll try again to
see if anyone has any tips. set up is like this I've got a web service that
can fetch large files from either ftp or http, when a file is fetched with
one of these protocols, a new thread is started and downloads
17 matches
Mail list logo