Hmm. Are you listing your persistent types in your persistence.xml
file? If not, what happens if you list them? If that doesn't fix
things, can you post your persistence.xml file?
-Patrick
On 9/6/07, Johan Andrén <[EMAIL PROTECTED]> wrote:
> I have not run the enhancer on the classes, and I'm not
I have not run the enhancer on the classes, and I'm not running the
runtime enhancer. I just found out how to pass arguments to the test
JVM earlier this afternoon so I'll test to use the runtime enhancer
as well as your proposed tests tomorrow.
This is the stacktrace:
testGetCurrentQuesti
Oh, and can you post the full stack trace?
-Patrick
On 9/6/07, Patrick Linskey <[EMAIL PROTECTED]> wrote:
> Hi,
>
> A bunch of questions:
>
> What happens if you check to see if one of your persistent classes is
> instanceof org.apache.openjpa.enhance.PersistenceCapable?
>
> Are you running the O
Hi,
A bunch of questions:
What happens if you check to see if one of your persistent classes is
instanceof org.apache.openjpa.enhance.PersistenceCapable?
Are you running the OpenJPA enhancer, or relying on the new unenhanced support?
If the instanceof check passes, what happens if you manually
Hi
I have a strange problem with OpenJPA and I have had no success
finding a solution on the net (yet).
We have a multi module maven2 project, the subprojects interesting in
this case beeing a data model with annotated classes - "model" and
ejb3 beans accessing the data - "ejb".
I have
Well, the short story is that if you comment out the load-time weaver
declaration in your applicationContext.xml, the problem goes away.
When the load-time weaver is specified, I believe that the problem is
caused by the fact that your main class also is your Spring bean. When
the load-time weaver
Yep, it's some sort of a classloader issue. Somehow, PersitenceCapable
is available in two different classloaders. I'll know more later today
/ tomorrow.
-Patrick
On 8/30/07, ben short <[EMAIL PROTECTED]> wrote:
> My test apps not rocket science so feel free to make a test case for
> it. But coul
My test apps not rocket science so feel free to make a test case for
it. But could you alter the packages names please.
On a site note, is it possible that the releases could make there way
into the main maven 2 repositories? The how to docs can be found here
[1] although you might allready know t
> Setting openjpa.RuntimeUnenhancedClasses=2 allows the application to
> run.
Cool; FTR, 2 corresponds to the 'warn' setting. Sorry about the
incorrect setting earlier.
> If i change it to the following and comment out the work around
> openjpa.RuntimeUnenhancedClasses then the application compla
Setting openjpa.RuntimeUnenhancedClasses=2 allows the application to
run. I'm using spring with the following loadTimeWeaver on my
entityManagerFactory...
org.springframework.instrument.classloading.SimpleLoadTimeWeaver
If i change it to the following and comment out the work around
openjpa.Runti
> I download the 1.0.0 source and ran mvn install. It built and
> installed ok. I use either the maven enhance plugin or the ant task to
> enhance the classes. When I run my simple test app I get the following
> exception...
Is there any way we could get access to that test application? I kinda
su
Hi,
I download the 1.0.0 source and ran mvn install. It built and
installed ok. I use either the maven enhance plugin or the ant task to
enhance the classes. When I run my simple test app I get the following
exception...
32 openjpa INFO [main] openjpa.Runtime - Starting OpenJPA 1.0.0
438 ope
12 matches
Mail list logo
