JPOX throws JDOFatalInternalException for queries using "new MyClass(...)" in result clauses

• Key: JDO-249
• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Andy Jefferson
• Reporter: Michael Watzek
• Component/s: tck2

Description

Test case ResultClassRequirements fails for the query below. The query has a constructor call in the result clause.

14:23:07,781 (main) DEBUG [org.apache.jdo.tck] - Executing API query: SELECT new LongString(personid, lastname) FROM org.apache.jdo.tck.pc.company.FullTimeEmployee IMPORTS import org.apache.jdo.tck.query.result.classes.LongString;
14:23:07,781 (main) INFO [org.apache.jdo.tck] - Exception during setUp or runtest:
javax.jdo.JDOFatalInternalException: The expression NewObjectExpression "" is not supported in results.
at org.jpox.store.query.ResultExpressionsQueryable.newResultObjectFactory(ResultExpressionsQueryable.java:251)
at org.jpox.store.query.JDOQLQuery.performExecute(JDOQLQuery.java:642)
at org.jpox.store.query.Query.executeWithMap(Query.java:966)
at org.jpox.store.query.Query.executeWithArray(Query.java:939)
at org.jpox.store.query.Query.execute(Query.java:862)
at org.apache.jdo.tck.query.QueryTest.execute(QueryTest.java:1151)
at org.apache.jdo.tck.query.QueryTest.execute(QueryTest.java:1029)
at org.apache.jdo.tck.query.QueryTest.executeAPIQuery(QueryTest.java:966)
at org.apache.jdo.tck.query.QueryTest.executeAPIQuery(QueryTest.java:946)
at org.apache.jdo.tck.query.result.ResultClassRequirements.executeQuery(ResultClassRequirements.java:464)
at org.apache.jdo.tck.query.result.ResultClassRequirements.testConstructor(ResultClassRequirements.java:436)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at junit.framework.TestCase.runTest(TestCase.java:154)
at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:204)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at junit.textui.TestRunner.doRun(TestRunner.java:116)
at junit.textui.TestRunner.doRun(TestRunner.java:109)
at org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java:120)
at org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:95)

Comments

[Andy Jefferson]

The title was a very sweeping statement and in fact the situation is that "new MyClass(...)" is not fully supported. Functionality is prioritised relative to what users require and this has been lower down the list

[Andy Jefferson]

Gone to meet its maker. Fixed in JPOX CVS - builds dated 09/01/2006 or later should have this.