[ http://issues.apache.org/jira/browse/JDO-377?page=all ]
Michael Bouschen updated JDO-377:
---------------------------------
Attachment: JDO-377-mbo.patch
Attached you find a new patch JDO-377-mbo.patch fixing a bug in the
LifecycleCompletetness class and adding three new configurations one for each
CompanyFactory implementation.
There is one configuration failing when running with the latest JPOX version
(I'm using the jars attached to JDO-375): lifecyclecompletenessPMInterface.conf
with applicationidentity. Method verifyOids checks that the target class of a
SingleFieldIdentity oid is the class passed to the pm.newInstance call (see
last paragraph of 12.6.6. on page 116 of the spec). In this configuration
pm.newInstance is called with a PC interface, but the target class is the
implementing class that was generatd by JPOX.
> 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-mbo.patch, 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
