Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Message-ID: <30144717.1145492195785.JavaMail.jira@brutus>
Date: Thu, 20 Apr 2006 00:16:35 +0000 (GMT+00:00)
From: "Craig Russell (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Subject: [jira] Commented: (JDO-369) Completeness test doesn't clean up
 instances of persistent interfaces
In-Reply-To: <10875038.1145398997686.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/JDO-369?page=comments#action_12375221 ] 

Craig Russell commented on JDO-369:
-----------------------------------

The patch looks good. Assuming that all the tests except for companyPMInterface pass, it's good to be checked in.


> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira