Apache JDO Project - [jira] Closed: (JDO-145) Remove pm.deletePersistent from fieldtypes

This is Interesting: Free IT Magazines  
Home > Archive > Apache JDO Project > April 2006 > [jira] Closed: (JDO-145) Remove pm.deletePersistent from fieldtypes





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author [jira] Closed: (JDO-145) Remove pm.deletePersistent from fieldtypes
Michael Bouschen (JIRA)

2006-04-24, 7:58 am

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

Michael Bouschen closed JDO-145:
--------------------------------

Fix Version: JDO 2 beta
Resolution: Fixed

> Remove pm.deletePersistent from fieldtypes tests
> ------------------------------------------------
>
> Key: JDO-145
> URL: http://issues.apache.org/jira/browse/JDO-145
> Project: JDO
> Type: Bug


> Components: tck20
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 2 beta


>
> The fieldtypes tests delete the persistent instance that they create at the end of the test using pm.deletePersistent(). Now that we use the new cleanup mechanism (addTearDownClass(Class)), there is no reason to deletie the instance. Also, the new mav

en option jdo.tck.cleanupaftertest cannot override this cleanup, so you can never see the database contents for debugging. Therefore, we should remove the line that deletes the persistent instance.

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


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com