The TCK test Instanceof has an error.
It defines 2 queries, yet only 1 set of expected results, ending up with
ArrayOutOfBoundsException when trying to get the expected result for the second
part.
--
Andy
Hi Andy,
check in done (see r330776).
Regards Michael
Hi Andy,
you are right, this is a bug in the test case. I'll change this soon.
Regards Michael
The TCK test ImplicitParameters has an error currently. The testFilter
has a query using firstname = :param.
This should be changed to
[ http://issues.apache.org/jira/browse/JDO-163?page=all ]
Michael Watzek updated JDO-163:
---
Attachment: JDO-163.patch2
The second patch implements the comments above.
Implement new JDO 2 query tests cases concerning query API Extensions
Hi Andy,
the fix works fine.
Thanks,
Michael
Hi Michael,
Please have a look.
Did that and its now fixed in JPOX CVS.
--
Andy
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL
[ http://issues.apache.org/jira/browse/JDO-198?page=all ]
Michelle Caisse closed JDO-198:
---
Fixed. Back to original problem as per JDO-98.
TestArrayCollections java.lang.IllegalArgumentException: out of field index
:28
Hi Michael,
thanks for your changes.
I don't understand why you changed the expected result to be emp3, emp4. The
query is looking for Employees that have a mentor field that is
PartTimeEmployee.
That means that it should return emp2 and emp3. The query is *not* which
employees *are*
Hi Andy,
Hi Michael,
thanks for your changes.
I don't understand why you changed the expected result to be emp3, emp4. The
query is looking for Employees that have a mentor field that is
PartTimeEmployee.
That means that it should return emp2 and emp3. The query is *not* which
employees *are*
[ http://issues.apache.org/jira/browse/JDO-173?page=all ]
Andy Jefferson resolved JDO-173:
Resolution: Fixed
Implemented in JPOX CVS. Test passes with builds dated 05/11/2005 or later
JPOX does not support instanceof operator
1. Test status (Michael W) 6 configs fail of 28. alltests: 5 F 15 E /
448 app ds identity
2. Query tests (Michael W)
MW submitted second patch for JDO-163. Continued working on 164. Need
improved result check for floats Methods should be generic and
available to other tests outside
Javadogs,
Currently there is no metadata that allows deployment to specify a
more specific type for the elements of an array. This is needed in
cases where the array is a generic type or an interface type and the
actual type is known at deployment time.
Proposal:
!ATTLIST array
Javadogs,
We need a way to determine whether a JDO implementation supports
various mapping features. Specifically:
Heterogeneous collections with new-class mapping of subclasses
Mapping fields of Object type and interface types
Craig Russell
Architect, Sun Java Enterprise System
[ http://issues.apache.org/jira/browse/JDO-98?page=comments#action_12356815
]
Craig Russell commented on JDO-98:
--
Issue 137 has been raised on the JDO expert group to allow specification of
element-type for array. This will allow us to specify
Hi Andy,
you are right, NotEquals is comparing floating point values using != and
in general this is not a good idea (BTW, the same holds true for class
Equality).
This is a old test that came from JDO1 and AFAIK it has not been changed
since then. So I'm wondering why it is failing now.
orm.xsd and unit tests for xsd are missing
--
Key: JDO-202
URL: http://issues.apache.org/jira/browse/JDO-202
Project: JDO
Type: Bug
Components: api20
Reporter: Michelle Caisse
Assigned to: Michael Bouschen
The xsd
Remove vendor extensions from TCK metadata
--
Key: JDO-203
URL: http://issues.apache.org/jira/browse/JDO-203
Project: JDO
Type: Bug
Components: tck20
Reporter: Michelle Caisse
Assigned to: Michelle Caisse
For
Need attribute on field element for type
Key: JDO-204
URL: http://issues.apache.org/jira/browse/JDO-204
Project: JDO
Type: Bug
Components: api20
Reporter: Michelle Caisse
Assigned to: Craig Russell
Need to supply
Write new test case for mapping Object and SimpleInterface without specifying
their specific type
-
Key: JDO-205
URL: http://issues.apache.org/jira/browse/JDO-205
Project: JDO
Javadogs,
Did we really intend for the single string version of JDOQL to
include IMPORTS import...?
setFilter(SELECT e FROM EMPLOYEE e WHERE e.grade
HardClass.HIGHEST_GRADE);
declareImports(import org.apache.jdo.tck.SimpleClass; import
org.apache.jdo.tck.HardClass;
pm.newQuery(SELECT
[ http://issues.apache.org/jira/browse/JDO-201?page=all ]
Michelle Caisse closed JDO-201:
---
Resolution: Fixed
revision 330953
Also added code block with logic to test BigDecimal fields.
TestArrayListCollections ClassCastException
JDOQL test NotEquals comparing floating point numbers
-
Key: JDO-206
URL: http://issues.apache.org/jira/browse/JDO-206
Project: JDO
Type: Bug
Components: tck20
Reporter: Andy Jefferson
The current TCK
20 matches
Mail list logo