openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Curtis <curti...@gmail.com>
Subject Re: Get nonsensical "column that is not compatible" error after replacing 1.2.1 with 1.2.2
Date Fri, 22 Jan 2010 17:41:04 GMT
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?

Thanks,
Rick

On Fri, Jan 22, 2010 at 10:13 AM, KARR, DAVID (ATTCINW) <dk068x@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.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message