You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Martin Zaun (JIRA)" <ji...@apache.org> on 2006/03/03 17:52:41 UTC
[jira] Updated: (JDO-299) Signature test needed checking compliance
of implementations with JDO2.0 API
[ http://issues.apache.org/jira/browse/JDO-299?page=all ]
Martin Zaun updated JDO-299:
----------------------------
Attachment: api20_defs.txt
This test uses reflection to verify that a set of JDO2.0 API classes conforms with the specification.
Since the number of features to be tested is quite large (~690 interfaces, classes, methods, or constants),
the feature definitions are not hard-coded into the test but parsed from a text file -- see attached file.
The format of the feature definition file is simple to parse, read, and maintain: basically, it's a stripped
version of the JDO2.0 Java interface and class sources.
> Signature test needed checking compliance of implementations with JDO2.0 API
> ----------------------------------------------------------------------------
>
> Key: JDO-299
> URL: http://issues.apache.org/jira/browse/JDO-299
> Project: JDO
> Type: Task
> Components: tck20
> Reporter: Martin Zaun
> Assignee: Martin Zaun
> Priority: Minor
> Fix For: JDO 2 final
> Attachments: api20_defs.txt
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira