> -----Original Message----- > From: Rick Curtis [mailto:curti...@gmail.com] > Sent: Friday, January 22, 2010 9:41 AM > To: users@openjpa.apache.org > Subject: Re: Get nonsensical "column that is not compatible" error > after replacing 1.2.1 with 1.2.2 > > David - > > I looked at the files that you uploaded and I'm somewhat confused... it > appears that the trace is from when you ran the enhancer, not when you > ran > the actual test case. By any chance can you boil this down to a simple > unit > test that I can use to recreate on my system?
The build output has the enhancer output and the output from the unit test. The enhancer output is at the beginning, followed by other output. I will try to work on a "standalone" test case, but that will take quite a while. > On Fri, Jan 22, 2010 at 10:13 AM, KARR, DAVID (ATTCINW) > <dk0...@att.com>wrote: > > > I added "class" elements for all of the entity classes listed in my > > orm.xml files, but the results were the same. > > > > I already have the following property set: > > > > <property name="openjpa.Log" value="DefaultLevel=TRACE, > > Runtime=TRACE"/> > > > > I assume that's what you need for tracing? > > > > By "filebin", I assume you mean <http://filebin.ca/>? I uploaded a > zip > > file containing my ant build output, unit test results, > persistence.xml, > > and orm.xml files, at <http://filebin.ca/cnmfge/metadataproblem.zip>. > > The ant build output shows the metadata trace results, and the unit > test > > results shows the exception. > > > >
