Apache JDO Project - Bug in XML testdata

This is Interesting: Free IT Magazines  
Home > Archive > Apache JDO Project > August 2005 > Bug in XML testdata





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Bug in XML testdata
Michael Watzek

2005-08-24, 5:46 pm

Hi,

I think I found a bug in XML testdata files wrt bidirectional
relationships. Values in the following fields did not match:

- Department.company <-> Company.departments:
- Employee.fundingDept <-> Department.fundedEmps
- Project.reviewers <-> Employee.reviewedProjects

Please find the attached patch for review.

Regards,
Michael
--
-------------------------------------------------------------------
Michael Watzek Tech@Spree Engineering GmbH
mailto:mwa.tech@spree.de Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http://www.spree.de/
-------------------------------------------------------------------

Michael Bouschen

2005-08-26, 2:45 am

Hi Michael,

thanks for the patch, I checked it in.

I noticed some new errors when running the alltests configuration with
datastoreidentity today.
ERROR XSAI2: The conglomerate (25.953) requested does not exist.

Actually 79 tests fail with that error message. I figured out that it has
nothing to do with your changes, so I decided to check them in.

Regards Michael

> Hi,
>
> I think I found a bug in XML testdata files wrt bidirectional
> relationships. Values in the following fields did not match:
>
> - Department.company <-> Company.departments:
> - Employee.fundingDept <-> Department.fundedEmps
> - Project.reviewers <-> Employee.reviewedProjects
>
> Please find the attached patch for review.
>
> Regards,
> Michael
> --
> -------------------------------------------------------------------
> Michael Watzek Tech@Spree Engineering GmbH
> mailto:mwa.tech@spree.de Buelowstr. 66
> Tel.: ++49/30/235 520 36 10783 Berlin - Germany
> Fax.: ++49/30/217 520 12 http://www.spree.de/
> -------------------------------------------------------------------
>



--
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


Michelle Caisse

2005-08-26, 2:45 am

Hi Michael and Michael,

I updated and ran a clean build and I don't see this error. It must
have been caused by some cruft on your machine. One possible cause is
that, if you allow maven to automatically upload the latest jpox builds
and then do "maven build", you will run with the latest enhancer code,
but your enhanced classes may have been created with the previous
version of the enhancer. You have to remember to manually delete the
old enhanced classes or to run "maven rebuild" each time you get a new
jpox build. I suppose that in maven.xml we could put a dependency of
the enhanced classes on the jpox enhancer in the uptodate test, but it
seems a bit unorthodox.

-- Michelle

Michael Bouschen wrote:

>Hi Michael,
>
>thanks for the patch, I checked it in.
>
>I noticed some new errors when running the alltests configuration with
>datastoreidentity today.
>ERROR XSAI2: The conglomerate (25.953) requested does not exist.
>
>Actually 79 tests fail with that error message. I figured out that it has
>nothing to do with your changes, so I decided to check them in.
>
>Regards Michael
>
>
>
>
>
>
>



Michael Bouschen

2005-08-28, 5:45 pm

Hi Michelle,

thanks for the hint. I did a clean build today and the problem disappeared.

Regards Michael

> Hi Michael and Michael,
>
> I updated and ran a clean build and I don't see this error. It must
> have been caused by some cruft on your machine. One possible cause is
> that, if you allow maven to automatically upload the latest jpox
> builds and then do "maven build", you will run with the latest
> enhancer code, but your enhanced classes may have been created with
> the previous version of the enhancer. You have to remember to
> manually delete the old enhanced classes or to run "maven rebuild"
> each time you get a new jpox build. I suppose that in maven.xml we
> could put a dependency of the enhanced classes on the jpox enhancer in
> the uptodate test, but it seems a bit unorthodox.
>
> -- Michelle
>
> Michael Bouschen wrote:
>
>
>



--
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


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com