[ http://issues.apache.org/jira/browse/JDO-230?page=comments#action_12359873 ]
Michael Bouschen commented on JDO-230: -------------------------------------- The patch looks good, no comments. > Fix order of makePersistent() and addTearDownClass() in localSetUp methods > -------------------------------------------------------------------------- > > Key: JDO-230 > URL: http://issues.apache.org/jira/browse/JDO-230 > Project: JDO > Type: Bug > Components: tck20 > Reporter: Michael Watzek > Assignee: Michael Watzek > Priority: Minor > Fix For: JDO 2 beta > Attachments: JDO-230.patch > > The order of calls makePersistent() and addTearDownClass() in localSetUp > methods is significant: addTearDownClass() must be called before > makePersistent(). This ensures that the next test run will cleanup the > database. > Currently, many tests call makePersistent() before addTearDownClass(). Given > that there is data in the database that will cause a duplicate key exception, > the database will not be cleaned up, because tear down classes have not been > added at the time the exception is thrown. -- 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
