Re: TCK completeness interface

Thu, 06 Apr 2006 07:06:50 -0700 

Hi Erik,
Great news. If you are this far, then you have succeeded in storing and retrieving instances to the database. I'll have a fix for you shortly. 

Craig

On Apr 6, 2006, at 4:06 AM, Erik Bengtson wrote:


Craig,


The "null" issue is over. It was a reachability issue where JPOX  
nullify all

fields before deleting from the database.


Now there is another issue in the CompletenessTest.test method  
where it falls
the expected object tree back to the concrete classes. It compares  
a concrete

object tree to the tree of objects generated by JPOX.


The code has a cast to Department and invoke to compareTo, and this  
code will

not work for interfaces.


    [java] 1) test(org.apache.jdo.tck.mapping.CompletenessTest) 
java.lang.ClassCa

stException: org.apache.jdo.tck.pc.company.IDepartmentImpl

    [java]      at org.apache.jdo.tck.pc.company.Department.compare 
(Department.j

ava:297)
    [java]      at java.util.Arrays.mergeSort(Arrays.java:1284)
    [java]      at java.util.Arrays.sort(Arrays.java:1223)
    [java]      at java.util.Collections.sort(Collections.java:159)

    [java]      at org.apache.jdo.tck.util.EqualityHelper.deepEquals 
(EqualityHel

per.java:477)

    [java]      at  
org.apache.jdo.tck.pc.company.Company.deepCompareFields(Compa

ny.java:224)

    [java]      at org.apache.jdo.tck.mapping.CompletenessTest.test 
(Completeness

Test.java:108)




Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!




Attachment:
smime.p7s

Description: S/MIME cryptographic signature






















					Reply via email to