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] Commented: (JDO-354) org.apache.jdo.tck.api.persistencemanager.lifecycle.MakePersistent may fail on teardown
Date Tue, 28 Mar 2006 17:33:19 GMT
    [ http://issues.apache.org/jira/browse/JDO-354?page=comments#action_12372125 ] 

Michelle Caisse commented on JDO-354:
-------------------------------------

Comment by Michael Watzek:

configurations "schemaAttributeOrm.conf" (Mapping 5), "schemaAttributePackage.conf" (Mapping
6), and "schemaAttributeClass.conf" (Mapping 7) run test MakePersistent which inherits from
PersistenceManagerTest.

Class PersistentManagerTest implements localSetUp adding tear down classes PCRect, PCPoint,
Department, and Company. But Department and Company are not contained in Mappings 5, 6, and
7. I propose to redefine localSetUp in MakePersistent accordingly.

Perhaps it makes sense to add a comment to ORM metadata of mappings 5, 6, and 7. All of these
mappings overwrite the default schema name passed as PMF property. Those mappings  assign
a schema name which does not comply to our schema name convention <identitytype><mapping>.
A comment would just be helpful to understand that this is done on purpose. 

> 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
>      Fix For: JDO 2 final

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