| Craig Russell (JIRA) 2006-03-30, 11:57 pm |
| [ http://issues.apache.org/jira/brows...action_12372169 ]
Craig Russell commented on JDO-354:
-----------------------------------
Two comments:
1. The patch looks good. I think this should solve the issue. Ok with me to check it in.
2. I think the description in the .conf files is too cryptic. I read it a few times and was still confused as to exactly what it was doing. It might help if you had a bit more text in the description.
MakePersistent test with schema name specified as class attribute in orm for PCPoint. The schema name derived from jdo.tck.mapping 7, e.g. applicationidentity7, is overriden in the file org/apache/jdo/tck/pc/PCPoint.orm to specify schema e.g. application
identity_cls.
MakePersistent test with schema name specified as package attribute in orm for PCPoint. The schema name derived from jdo.tck.mapping 7, e.g. applicationidentity6, is overriden in the file applicationidentity/org/apache/jdo/tck/pc/package-standard6.orm to
specify schema e.g. applicationidentity_pkg.
I probably got this wrong, but you get the idea.
[vbcol=seagreen]
> org.apache.jdo.tck.api.persistencemanager.lifecycle.MakePersistent may fail on teardown
> ---------------------------------------------------------------------------------------
>
> Key: JDO-354
> URL: http://issues.apache.org/jira/browse/JDO-354
> Project: JDO
> Type: Bug
> Components: tck20
> Versions: JDO 2 beta
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 2 final
> Attachments: JDO-354.patch
>
> When invoked from a configuration that does not use the default schema, MakePersistent fails because it queries for classes to tear down that do not exist in the current schema.
> testMakePersistent
--
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
|