Hi,

[...]

Michael also sees failures with two other tests that may be related to using the latest Derby release. AI Michael: verify relationship to Derby version and follow up with email or JIRA.
I see the configuration companyMapWithoutJoin.conf sporadically failing, because a map SCO does not have the expected value. It has nothing to do with the derby version, it was just a coincidence that I noticed it the first time when I tried the latest derby version. I was able to reproduce the problem with the old derby version.

The configuration uses a modified company model where Department has a map of employee instances and a new Employee field called role is the key in the map. The testdata provides a value for the role field in employee and for the key in the map. But the factory to create the instances does not populate the role field in employee. So there is an inconsistency between the key in the map (has a value) and the employee field (is null) used to map the key to the database. I enabled the JPOX RDBMS logger and saw that in the case of a failure there is an employee INSERT statement with NULL as the value for the ROLE column.When loading the corresponding department instance the map of employee misses this entry because the key is null. The fix is easy: the factory needs to set the role field when creating the employee instance.

I will file a JIRA and provide a patch as soon as JIRA is up again.

Regards Michael

[...]

--
Michael Bouschen                [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]        http://www.tech.spree.de/
Tel.:++49/30/235 520-33         Buelowstr. 66                   
Fax.:++49/30/2175 2012          D-10783 Berlin                  

Reply via email to