I read through that Issue a bit closer and this particular user found the message to appear when he was missing the @Id annotation somewhere in his Entity classes (any one of them)...
*"Furthermore, I was able to identify that the error message was being printed only when I removed the @Id annotation from one of my classes (all the other classes still have @Id)."* Good luck, Kevin On Thu, Dec 17, 2009 at 8:16 AM, Kevin Sutter <[email protected]> wrote: > Unfortunately, this problem [1] has been around for a long time. It seems > to come and go. Nobody has taken the time to completely figure out the > problem and solution. > > If I remember my own experiences with this error message, I believe it came > up more often with the fallback enhancement plan of subclassing. Do you > pre-enhance your classes during the build or use a javaagent to do the > enhancement processing? If you don't explicitly enhance your entity > classes, then you are falling back to the subclassing support which should > not be used for production... > > I may be all wet with my memory and this may be due to something else, but > that's what I recollect... > > Good luck! > Kevin > > [1] https://issues.apache.org/jira/browse/OPENJPA-428 > > > On Thu, Dec 17, 2009 at 6:31 AM, Mark Struberg <[email protected]> wrote: > >> Got the following problem reported in OpenJPA-2.0.0-M3 >> >> openjpa.Runtime - The configuration property named "openjpa.Id" was not >> recognized and will be ignored, although the name closely matches a valid >> property called "openjpa.Id". >> >> LieGrue, >> strub >> >> __________________________________________________ >> Do You Yahoo!? >> Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz >> gegen Massenmails. >> http://mail.yahoo.com >> > >
