db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michelle Caisse (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JDO-354) org.apache.jdo.tck.api.persistencemanager.lifecycle.MakePersistent may fail on teardown
Date Tue, 28 Mar 2006 23:07:19 GMT
     [ http://issues.apache.org/jira/browse/JDO-354?page=all ]

Michelle Caisse updated JDO-354:
--------------------------------

    Attachment: JDO-354.patch

This simple patch gives the following results with an otherwise clean build & latest JPOX
download:
    [java] Total tests run: 1239. Failures: 1, Errors: 2.
    [java] 3 of 57 configurations failed.

I didn't modify the orm files as Michael suggested because we do explain the schema override
in the .conf files.  If anyone else feels that we should also add comments to the orm files
or improve the description in the .conf files, I would be happy to make that change.  Currently
we say:
jdo.tck.description = MakePersistent test with schema name specified as class attribute in
orm for PCPoint. Schema name derived from jdo.tck.mapping 1 is overriden in orm

[jdo.tck.mapping 1 is wrong.  I should see jdo.tck.mapping 7 (or 6, or 5)]


> 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
> > > (org.apache.jdo.tck.api.persistencemanager.lifecycle.MakePersistent)
> > > javax.jdo.JDOFatalException:
> > > Exception during tearDown
> > > 	at org.apache.jdo.tck.JDO_Test.tearDown(JDO_Test.java:329)
> > > 	at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:251)
> > > 	at org.apache.jdo.tck.util.BatchTestRunner.doRun
> > > (BatchTestRunner.java:107)
> > > 	at org.apache.jdo.tck.util.BatchTestRunner.start
> > > (BatchTestRunner.java:147)
> > > 	at org.apache.jdo.tck.util.BatchTestRunner.main
> > > (BatchTestRunner.java:122)
> > > NestedThrowablesStackTrace:
> > > javax.jdo.JDODataStoreException: Error executing JDOQL query "SELECT
> > > THIS.DEPARTMENT_ID,THIS.DEPTID,THIS."NAME" FROM
> > > datastoreidentity7.DEPARTMENT
> > > THIS" : Schema 'DATASTOREIDENTITY7' does not exist
> > > ERROR 42Y07: Schema 'DATASTOREIDENTITY7' does not exist

-- 
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


Mime
View raw message