Yes, I've been using build time enhancement - runtime was there for fast
prototyping in rare cases build time enhancement did not run for whatever
reason.
I removed it as you suggested to be consistent always.
Thanks!
Krzysztof
--
View this message in context:
Hi,
created an issue for it. Thanks for your ideas to make the cache disablement
query based
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
Am 02.03.2011 um 19:10 schrieb Jeremy Bauer:
Marc,
I'm glad that worked for you. You could actually just exclude
No problem. I'm happy to hear that you are up and running.
-Jeremy
On Wed, Mar 2, 2011 at 11:26 PM, Phill ph...@bicispace.com wrote:
Many thanks Jeremy, to my embarrassment I've discovered that lead wasn't
getting set properly on the other end of the association. I jumped to the
wrong
Hi,
I am using Apache Derby with OpenJPA and have a class with a named query.
Unfortunately, every time I attempt to execute the named query I get an
error because OpenJPA is assuming the USER schema. The USER schema is
not the default for Derby. It is APP I think. This does not happen when
I
As suspected something strange with the class loaded and entities (POJOs)
used in a web service... Stripped the openjpa jar to
PersistenceCapable.class, put that into ear - worked
--
View this message in context: