[ http://issues.apache.org/jira/browse/JDO-377?page=all ]

Craig Russell updated JDO-377:
------------------------------

    Attachment: JDO-377.patch
                lifecyclecompleteness.conf
                LifecycleCompleteness.java

Please review these changes.

In addition to the changes mentioned, a bug was fixed in CompletenessTest where 
the tearDown classes are obtained always from the default reader, not the 
reader used for persistent instances.



> Company model factory improvements to test persistent interfaces
> ----------------------------------------------------------------
>
>          Key: JDO-377
>          URL: http://issues.apache.org/jira/browse/JDO-377
>      Project: JDO
>         Type: Improvement

>   Components: tck20
>     Versions: JDO 2 rc1
>     Reporter: Craig Russell
>     Priority: Minor
>      Fix For: JDO 2 final
>  Attachments: JDO-377.patch, LifecycleCompleteness.java, 
> lifecyclecompleteness.conf
>
> Please review this patch.
> In order to test persistent interfaces better, a method was added to the 
> CompanyFactory interface to allow the test program to get the persistent 
> instances. 
> List getAllInstances();
> To implement this new API, changes were made to the factory implementation 
> classes to keep track of instances as they were created.
> Additionally, only classes (or interfaces) actually instantiated were put 
> into the tearDown class array. So Person.class and Employee.class were 
> removed from the array.
> Finally, a bug was fixed in CompanyFactoryPMClass where the interface 
> IMedicalInsurance.class was incorrectly added to the tearDown class array.
> A new test class was used for testing. This class might be added to the TCK 
> if suitable.
> And a new configuration was used for testing. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to