Go ahead and open a JIRA. I'll try to find a few cycles this afternoon to
look at it.

-- 
Thanks,
Rick

On Tue, Jan 26, 2010 at 11:26 AM, KARR, DAVID (ATTCINW) <[email protected]>wrote:

> > -----Original Message-----
> > From: Rick Curtis [mailto:[email protected]]
> > Sent: Friday, January 22, 2010 9:41 AM
> > To: [email protected]
> > 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?
>
> I've set up a testcase project that you should be able to use to
> demonstrate this problem.  I don't know if I could call it a "simple"
> unit test, as the zip file without dependent jars is 100k, but the whole
> test will run from "ant" on the command line.  Should I file a ticket
> for this, or send it to you directly?
>
> > On Fri, Jan 22, 2010 at 10:13 AM, KARR, DAVID (ATTCINW)
> > <[email protected]>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.
> > >
> > >
>

Reply via email to