The idea is that Toplink JPA supports that feature. OpenJPA - no.
Maybe this can be done as some configurable behaviour ?
They do, but really, all that they are doing is hiding the open EM. In
other words, the objects are not actually really detached yet.
What type of application are you
I get this. What's this refid for?
build.xml:91: Reference cp not found.
klaasjan elzinga wrote:
My ant script looks like:
taskdef name=openjpac
classname=org.apache.openjpa.ant.PCEnhancerTask
classpath refid=cp/
It is a reference to a path defined somewhere else in the build.xml
file. It is typically used when a classpath or a path has to be used
in several places in the file. You can find the doc for this at
http://ant.apache.org/manual/index.html
Click on the Concept and Types link and then click on
Its the classpath, containing the required jars. Construct it using
the path element.
KJ
On 9/12/07, Stanczak Group [EMAIL PROTECTED] wrote:
I get this. What's this refid for?
build.xml:91: Reference cp not found.
klaasjan elzinga wrote:
My ant script looks like:
Another way to achieve this is to use different fetch plans for
different use cases, which will result in the right stuff being
detached in each context.
You would still need to manually tune what gets detached, of course.
And i'm kinda unwilling to inject EntityManager into those top-level
Native queries can only be SELECT statements per the spec; OpenJPA
assumes that if they don't start with SELECT, they're stored
procedures. That's what's causing the error.
The reason for this is that you can't do anything interesting (from a
JPA standpoint) with the results of such a query
Hi,
Can you post a thread dump? I think you can get one by hitting
control-shift-|, although I always end up hitting two or three things
before getting it.
-Patrick
On 9/11/07, Dave [EMAIL PROTECTED] wrote:
I'm trying to upgrade the Roller 4.0 code base from OpenJPA 0.9.7 to
OpenJPA 1.0 but
Hi,
Does anyone run into this error:
exception is openjpa-1.0.0-r420667:568756 fatal user error
org.apache.openjpa.persistence.ArgumentException:
com.inxight.mdr.dao.model.Sentence.text declares a column that is not
compatible with the expected type clob. Column details:
Full Name:
Hi Frank,
The thing that jumps out at me is the length. What did you intend -1
to mean? This should be the maximum length of data stored in the
column and really needs to be a good application-specific value.
Craig
On Sep 12, 2007, at 10:51 AM, frankca wrote:
Hi,
Does anyone run into
