Martin Desruisseaux wrote:
Jody Garnett a écrit :
Hi Marting, one of the joys of working on the FM branch is exposure
to the latest GenericName interface - as an example the
implementation of NamedIdentifier "breaks".... is the following patch
suitable?
/**
* @since GeoAPI 2.1
*/
public NameSpace scope() {
return getName().scope();
}
NameSpace is not yet implemented in Geotools, so it will not work
neither.
Every GeoAPI interface or method with a "@since 2.1" comment will
break Geotools build. GenericName is not the only one. There is also
new methods in CoordinateSystemAxis, Coverage, GridCoverage, Envelope,
CRSFactory, etc.
A possible patch is to implements empty skeleton for those methods in
GeoAPI, something like:
/**
* @since 2.3
*/
public NameSpace scope() {
// TODO: New GeoAPI 2.1 method
throw new UnsupportedOperationException("Not yet implemented.");
}
I suggest to put "@since 2.3" in the comment instead of "@since GeoAPI
2.1" because the @since tag is about the Geotools version when this
method were introduced. And the "// TODO: New GeoAPI 2.1" argument
will help me to perform a search in the whole code base on "GeoAPI
2.1" keyword, for spotting the methods that need to be implemented.
Could it work?
Sure - I will do this.
However any idea when to expect simplification of Generic Name? It
sounded like you and Bryce were having some great ideas - but what I was
trying to stub in the fm branch still looked hard.
Jody
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
