db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Jefferson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-285) Fix list of teardown classes in company model reader.
Date Fri, 03 Feb 2006 18:39:04 GMT
    [ http://issues.apache.org/jira/browse/JDO-285?page=comments#action_12365106 ] 

Andy Jefferson commented on JDO-285:

Further comment : both of these issues are trying to read the results of queries, before the
connection is closed while rolling back). What is the query that was executed just before
? and what is the SQL invoked by JPOX ? (in the JPOX log). This should have a column "XXX
as JPOXMETADATA" or a discriminator column. This should define the type of the real object
in the datastore, and then JPOX is trying to create an instance of it. Is the SQL correct
for the query ? Is the value of this class being returned incorrectly and consequently JPOX
tries to create an instance of an abstract class (or rather JDOImplHelper.newInstance is asked
to but returns null for the class Employee ... why would it do that ?)

> Fix list of teardown classes in company model reader.
> -----------------------------------------------------
>          Key: JDO-285
>          URL: http://issues.apache.org/jira/browse/JDO-285
>      Project: JDO
>         Type: Bug
>   Components: tck20
>     Reporter: Michael Watzek
>     Assignee: Michael Watzek
>  Attachments: JDO-285.patch
> The list of teardown classes in company model should not contain subclasses of inheritance
hierarchies insurance and person. In t-conference, Jan 27, we agreed that the correct order
is: Insurance.class, Person.class, Department.class, Company.class, Project.class.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message