db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bouschen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JDO-369) Completeness test doesn't clean up instances of persistent interfaces
Date Wed, 19 Apr 2006 21:58:35 GMT
     [ http://issues.apache.org/jira/browse/JDO-369?page=all ]

Michael Bouschen updated JDO-369:

    Attachment: JDO-369.patch

This issue is related to JDO-327.

Attached you find a patch JDO-369.patch for review including two changes:
- Adding discriminator column to the schema and metadata files. This change is provided by
Erik; I just removed the index definition for the discriminator column from Erik's proposal.
- CompletenessTest gets the list of teardown classes from the CompanyFactory used by the CompanyModelReader
to create the company model instances.

> Completeness test doesn't clean up instances of persistent interfaces
> ---------------------------------------------------------------------
>          Key: JDO-369
>          URL: http://issues.apache.org/jira/browse/JDO-369
>      Project: JDO
>         Type: Bug

>   Components: tck20
>     Versions: JDO 2 rc1
>     Reporter: Craig Russell
>     Assignee: Michael Bouschen
>      Fix For: JDO 2 final
>  Attachments: JDO-369.patch
> The completeness test registers persistence-capable classes to be deleted at tearDown,
but it doesn't register persistence-capable interfaces. So the completeness test for persistent
interfaces fails the second time through.
> The suggested fix is for the CompanyModelReader to return persistence-capable interfaces
along with persistence-capable classes when called for the list of classes to clean up.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message