> -----Original Message----- > From: Rick Curtis [mailto:[email protected]] > Sent: Friday, January 22, 2010 7:02 AM > To: [email protected] > Subject: RE: Get nonsensical "column that is not compatible" error > after replacing 1.2.1 with 1.2.2 > > KARR, DAVID (ATTCINW) wrote: > > > > No. I never have. I only list the orm.xml files. > > > > Can you try listing your persistent types in the p.xml file to see if > this > problem goes away? If that doesn't work, can you turn on trace and post > it > to filebin so I can take a look at it?
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.
