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:
http://openjpa.208410.n2.nabble.com/Build-time-enhancement-or-GlassFish-enhancement
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 w
No problem. I'm happy to hear that you are up and running.
-Jeremy
On Wed, Mar 2, 2011 at 11:26 PM, Phill 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 conclusion about the i
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
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:
http://openjpa.208410.n2.nabble.com/
Hello Michael,
Big thanks for the hints - yes it's bizzare it worked this way indeed. One
explanation could be I was switching to "table" generator for Postgres
sometimes as there was some problem with sequence removal during schema
cleanup ("drop" action).
But I had used this sequence definition b
