Hey Rick, I passed the problem by removing the other persistence.xml. I'm using runtime enhancement, and by debuging I noticed that in some point the enhancer makes parsed.parse() for each peristence.xml. When the parsing ends, only the last parse is taking in count (within the parser._result) and that is the wrong persistence.xml in my case.. I'm pretty sure it's a bug..
On Tue, Jun 16, 2009 at 6:06 PM, Rick Curtis (via Nabble) < ml-user+172967-154794...@n2.nabble.com<ml-user%2b172967-154794...@n2.nabble.com> > wrote: > Udi - > > I wasn't able to find any changes from 1.0.1 -> 1.2.0 that would affect > your application, can you post some more information? > > Are you using buildtime or runtime enhancement? When you are enhancing, is > it possible that you are setting addDefaultConstructor to false? > > -Rick > > Udi wrote: > Hey, > I upgraded the OpenJPA version from 1.0.1 to 1.2.0 > Now my application fails due to missing no-args constructor. > I checked and noticed that the enhancer works on a persistence.xml locating > in another jar (which is part of my application, but not the wanted xml). > My persistence.xml is in the same META-INF as it was before but the > enhancer still won't see it. > > Was something changed with enhancement? > > > > ------------------------------ > This email is a reply to your post @ > http://n2.nabble.com/Runtime-enhancement-fails-tp3078746p3086895.html > You can reply by email or by visting the link above. > > -- View this message in context: http://n2.nabble.com/Runtime-enhancement-fails-tp3078746p3087372.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
