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-GlassF
--
View this message in context:
http://openjpa.208410.n2.nabble.com/Build-time-enhancement-or-GlassFish-enhancement-tp6061774p6067771.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
s don't crash into each other or get mixed up?
Best,
Laird
--
View this message in context:
http://openjpa.208410.n2.nabble.com/Build-time-enhancement-or-GlassFish-enhancement-tp6061774p6062142.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
Just to add to Rick's comments.
Where build time enhancement can really help you is if you run some
acceptance or unit tests before deploying to Glassfish. It's always nice to
test with the same bytecode that you deploy.
That said, it Glassfish should configure the automatic enhancement if you
us
I'd recommend taking the time to setup build time enhancement. You'll save
on headaches in the long run.
Thanks,
Rick
On Thu, Feb 24, 2011 at 2:13 PM, baboune wrote:
>
> H,
>
> Sorry for this stupid question but despite reading
> http://openjpa.apache.org/entity-enhancement.html
> http://openjp
equired correct?
/Thanks
--
View this message in context:
http://openjpa.208410.n2.nabble.com/Build-time-enhancement-or-GlassFish-enhancement-tp6061774p6061774.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
