Details
-
Type:
Test
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.0, 2.0
-
Fix Version/s: None
-
Component/s: conformance
-
Labels:
-
Number of attachments :
Description
GeoAPI interfaces were created mostly by hand. They may contains errors. A test suites comparing GeoAPI interfaces against OGC models is an essential part of the GeoAPI project. One possible approach is:
- Uses reflection (including the annotation mechanism available in
J2SE 1.5) for examining all interfaces are methods.
- For each entity found in the previous step, compare the name and
type against the information provided in UML.
HTML pages should be automatically generated with:
- A list of missing interfaces / methods;
- A list of GeoAPI convenience methods not part of OGC models;
- A list of significant (other than the "get" prefix) name change.
Issue Links
| This issue depends upon: | ||||
| GEO-17 | Use anotations instead of @UML tags |
|
|
|
This work is already partially done. @UML annotation are used for checking GeoAPI classes/methods name compliance to OGC/ISO ones. The result is the following page, automatically generated:
http://geoapi.sourceforge.net/snapshot/javadoc/org/opengis/doc-files/departures-list.html
But we need to go further and compare the @UML tags against the Rational Rose file content (either in Rational Rose format or translated in XMI format). This is essential in order to locate possible GeoAPI mistakes, and also for tracking ISO changes.