You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by Andy Jefferson <an...@jpox.org> on 2006/03/05 02:35:18 UTC
Re: svn commit: r382920 - in /db/jdo/trunk/tck20/src:
conf/configurations.list
orm/applicationidentity/org/apache/jdo/tck/pc/company/package-standard.orm
orm/datastoreidentity/org/apache/jdo/tck/pc/company/package-standard.orm
>The exception disappears when reverting the changes in
>company/package-standard.orm. Maybe the JPOX orm metadata parser does
>not yet accept the definition.
Doesn't yet accept *what* definition ?
The log always tells you what is parszed and what isn't and if any errors are
encountered.
--
Andy
Re: svn commit: r382920 - in /db/jdo/trunk/tck20/src: conf/configurations.list orm/applicationidentity/org/apache/jdo/tck/pc/company/package-standard.orm orm/datastoreidentity/org/apache/jdo/tck/pc/company/package-standard.orm
Posted by Erik Bengtson <er...@jpox.org>.
Hi,
I have some updates.
First, the recent problems with metadata are fixed in CVS.
Second, newer tests of interfaces creation requires the JPOX enhancer jar to be
in the runtime classpath. JPOX does not use proxy classes, but creates
PcCapable classes at runtime. This feature is not finished, so you may many
find issues.
And last, for the classes using native strategy and auto increment columns, the
PMF setting "org.jpox.initializePrimaryKeyColumnInfo" must be set to true. This
is not enabled by default.
For org.jpox.initializePrimaryKeyColumnInfo=true and JPOX-enhancer not in
classpath, this is my status
Total tests run: 1162. Failures: 4, Errors: 42.
33 of 52 configurations failed.
143 minutes!!!!
Regards,
Quoting Michael Bouschen <mb...@spree.de>:
> Hi Andy,
>
> >>The exception disappears when reverting the changes in
> >>company/package-standard.orm. Maybe the JPOX orm metadata parser does
> >>not yet accept the definition.
> >>
> >>
> >
> >Doesn't yet accept *what* definition ?
> >
> >
> The mailer must have skipped it: the definition of the element
> interface. I had put it in angle brackets which is not a good idea when
> using a html mailer.
>
> >The log always tells you what is parszed and what isn't and if any errors
> are
> >encountered.
> >
> >
> I attach the junit test output (derby-app-sometests-junit.txt) and the
> jpox log (derby-app-sometests-jpox.txt, I skipped a couple of messages,
> because the apache mailer does not accept mail over 100K) below. Maybe
> the memory result of the parsed metadata element does not have the
> expected class.
>
> Regards Michael
>
> >--
> >Andy
> >
> >
>
>
> --
> Michael Bouschen Tech@Spree Engineering GmbH
> mailto:mbo.tech@spree.de http://www.tech.spree.de/
> Tel.:++49/30/235 520-33 Buelowstr. 66
> Fax.:++49/30/2175 2012 D-10783 Berlin
>
>
Re: svn commit: r382920 - in /db/jdo/trunk/tck20/src: conf/configurations.list
orm/applicationidentity/org/apache/jdo/tck/pc/company/package-standard.orm
orm/datastoreidentity/org/apache/jdo/tck/pc/company/package-standard.orm
Posted by Michael Bouschen <mb...@spree.de>.
Hi Andy,
>>The exception disappears when reverting the changes in
>>company/package-standard.orm. Maybe the JPOX orm metadata parser does
>>not yet accept the definition.
>>
>>
>
>Doesn't yet accept *what* definition ?
>
>
The mailer must have skipped it: the definition of the element
interface. I had put it in angle brackets which is not a good idea when
using a html mailer.
>The log always tells you what is parszed and what isn't and if any errors are
>encountered.
>
>
I attach the junit test output (derby-app-sometests-junit.txt) and the
jpox log (derby-app-sometests-jpox.txt, I skipped a couple of messages,
because the apache mailer does not accept mail over 100K) below. Maybe
the memory result of the parsed metadata element does not have the
expected class.
Regards Michael
>--
>Andy
>
>
--
Michael Bouschen Tech@Spree Engineering GmbH
mailto:mbo.tech@spree.de http://www.tech.spree.de/
Tel.:++49/30/235 520-33 Buelowstr. 66
Fax.:++49/30/2175 2012 D-10783 Berlin