| Michael Bouschen (JIRA) 2006-04-29, 7:11 pm |
| [ http://issues.apache.org/jira/browse/JDO-375?page=all ]
Michael Bouschen updated JDO-375:
---------------------------------
Attachment: JDO-375.patch
I found one issue with the cleanup code in the CompletenessTest: it retriveves the list of tearDownClasses from the reader that is used to create the transient graph for comparison. But this reader returns the PC classes and not the PC interfaces. The att
ached patch JDO-375.patch fixes this bug.
However, cleanup still does not work. The cleanup code uses the following pattern (as Criag mentioned in the other email):
Query query = new Query();
query.setClass(ICompany.class);
query.setCandidates(pm.getExtent(ICompany.class, false));
pm.deletePersistentAll((Collection)query.execute());
I added some debug messages and figured out that the query using the extent of a persistent interface does not return any instances.
> Company model tables are not fully cleaned up
> ---------------------------------------------
>
> Key: JDO-375
> URL: http://issues.apache.org/jira/browse/JDO-375
> Project: JDO
> Type: Bug
[vbcol=seagreen]
> Components: tck20
> Versions: JDO 2 rc1
> Reporter: Erik Bengtson
> Assignee: Michael Bouschen
> Attachments: JDO-375.patch
>
> Tables from company model does not appear to be clean after run.
> I can't say if this is a JPOX or TCK issue, because I did not dig into the issue.
> On second run, exceptions are like
--
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
|