Michael Bedward a écrit :
> Reading the notes about operations from the perspective of a relative
> beginner, it's not clear to me what the reasons / pros / cons are for
> invoking an operation via Operations.DEFAULT (as with the resample
> example on the Use a GridCoverage page) versus using the
> DefaultProcessor.doOperation method.
Operations.DEFAULT is nothing else than a convenience wrapper around the
DefaultOperation.doOperation. It provides typesafe method signatures. However
it
does nothing else than packaging the parameters and delegates to
DefaultProcessor.doOperation.
I should probably drop the DEFAULT part (I will do that in geotidy).
This is a little bit like ReferencingFactoryFinder which is only a set of
convenience typesafe methods delegating to FactoryRegistry.
Martin
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
