Hello everybody,
I want to configure the openjpa.jdbc.SynchronizeMappings property in my
persistence.xml in a way that it...
1. ... drops all tables in the database schema (drop whole schema)
2. ... recreates the schema
3. ... builds tables for all entity classes
My Intention is, also to clear
Hi Rick,
thank you so much for your time you spent!
Aww, I knew, that there was a time I did not have that enhance-message, but I
thought I just imagined it ;)
I already used the InstrumentationLoadTimeWeaver some time before (that is why
it was commented out in db.xml), but got warning
Hello everybody,
I have got another problem. This time it is a problem with runtime enhancement.
I am enhancing my classes with the following ant script started from Eclipse:
project name=jpa_enhance_builder
path id=enhance.cp
pathelement
Hello Donald,
thank you very much for your answer.
I already heard of that plug-in and would use it in case of doubt. But because
of some security restrictions in my company also including Eclipse plug-ins, I
would prefer an Ant solution to be able to hand-off the project without forcing
Hi Rick,
I also had that thought, but the message lists all of my entities, so I think
they all have not been enhanced.
I oriented on the following tutorial for creating and invoking the build script:
http://webspherepersistence.blogspot.com/2009/04/openjpa-enhancement-eclipse-builder.html
I
Hey David,
thank you for the tip!
I checked one of my entities with javap:
1. After a clean and manually invoking the enhance task
2. After execution of my application
Both times the class has pc* methods, so it seems that they are enhanced and
not overwritten by Eclipse.
So why the error
Hi,
so far, I just worked with one binary folder and did not create jars from the
project, too. I checked the whole workspace and the eclipse classpath but did
not find any double classes or imports. I even removed all classes from the
binary folder and rebuilt them.
I debugged my application
Hi,
as far as I know, TopLink has a maximum fetching depth of 2 by default and
OpenJPA has an infinite fetching depth, which could lead to recursions in the
worst case if you use eager fetching.
I am wondering why this also happens with lazy fetching - did you forget to
enhance your classes?
Hi,
best, you have a look at the documentation:
http://people.apache.org/~mprudhom/openjpa/site/openjpa-project/manual/ref_guide_pc_enhance.html
OpenJPA classes need to be enhanced to provide lazy fetching. Else there will
always been used eager fetching, which could be the cause of your
