TCK : ImplicitParameters testResult

2005-11-05 Thread Andy Jefferson
The ImplicitParameters test has a test called testResult that puts a parameter in the result. Let's leave aside why anyone would want to do this, other than insanity :-) Looking at the result of the test (with JPOX CVS) I now get [java] expected: [[Ljava.lang.Object;@18e1286,

Re: TCK : ImplicitParameters testResult

2005-11-05 Thread Michael Bouschen
Hi Andy, you are right, the current implementation of testing the query result does not work in case of Object[]. Michael W. is currently working on adding new TCK classes testing the query result handling (JDO-164). He ran into the same problem and changed the code checking the query result

Re: svn commit: r330804 - /incubator/jdo/trunk/tck20/test/java/org/apache/jdo/tck/query/jdoql/variables/VariablesWithoutExtent.java

2005-11-05 Thread Michael Bouschen
Hi Craig, Javadogs, Did we really intend for the single string version of JDOQL to include IMPORTS import...? I agree, the leading IMPORTS keyword seems to be redundant. We followed the rule that all the query elements are prefixed with a new keyword in the single string version (WHERE

[jira] Assigned: (JDO-194) JPOX does not support implicit variables.

2005-11-05 Thread Andy Jefferson (JIRA)
[ http://issues.apache.org/jira/browse/JDO-194?page=all ] Andy Jefferson reassigned JDO-194: -- Assign To: Michael Watzek (was: Andy Jefferson) JPOX CVS does now implement implicit variables 9nightly builds dated 06/11/2005 or later), and the test