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] Created: (JDO-390) JPOX fails new test: change to projected Date field is reflected in the database
Date Sat, 24 Jun 2006 05:19:29 GMT
JPOX fails new test: change to projected Date field is reflected in the database

         Key: JDO-390
         URL: http://issues.apache.org/jira/browse/JDO-390
     Project: JDO
        Type: Bug

  Components: tck20  
    Versions: JDO 2 maintenance release 1    
    Reporter: Michelle Caisse
 Assigned to: Andy Jefferson 
     Fix For: JDO 2 maintenance release 1

Changes to a projected SCO should not be persisted to the data store. JPOX persists changes
to a projected Date field in the new query.result.ProjectedSCODoesNotTrackChanges test.
 [java] 1) testDateField(org.apache.jdo.tck.query.result.ProjectedSCODoesNotTrackChanges)junit.framework.AssertionFailedError:
    [java] Expected Company instance not to be dirty; actual state is {persistent, transactional,
    [java] Expected projected field value is Fri Jun 23 21:53:29 PDT 2006; actual value is
Wed Dec 31 16:02:03 PST 1969
    [java]      at org.apache.jdo.tck.JDO_Test.failOnError(JDO_Test.java:1052)
    [java]      at org.apache.jdo.tck.query.result.ProjectedSCODoesNotTrackChanges.testDateField(ProjectedSCODoesNotTrackChanges.java:150)
    [java]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [java]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [java]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
    [java]      at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:237)
    [java]      at org.apache.jdo.tck.util.BatchTestRunner.doRun(BatchTestRunner.java:107)
    [java]      at org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java:147)
    [java]      at org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:122)

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