[geotk] Explicit TIFF plugin register

[Martin Desruisseaux]

Hello all

Le 11/07/11 09:07, sorel johann a écrit :
> ImageIO do not use the usual meta-inf/service configuration for discovery of 
> new readers. It uses somekind of predecessor.

Actually the Image I/O module uses the META-INF/services configuration as much 
as possible, but there is a few cases where we did not succeed yet. This include 
readers that are wrappers around other readers. Both the "/World File reader/" 
and the GeoTIFF readers are wrappers around the standard TIFF reader, which 
delegate to the standard TIFF reader for image I/O operations and add geographic 
information to their IIOMetadata object.

The problem is that during the automatic Image I/O discovery phase by 
IIORegistry, we are not sure that the standard image readers are registered 
before the wrappers, and anyway attempts to get an other reader during the 
discovery phase doesn't seem to work. I have some idea about how to workaround 
(all of them require delaying the search for the standard reader at some later 
stage after the discovery phase) but did not experimented them yet.

In the main time, the Image I/O initialization is documented in the bottom of 
this page:

http://www.geotoolkit.org/apidocs/org/geotoolkit/image/io/package-summary.html

We are working toward more automatic initialization/shutdown process in the 
Geotk library, so I hope that you will see improvement happen progressively. For 
example for the upcoming 3.19 release I cleaned a little bit the background 
threads, relying more on ScheduledThreadPoolExecutor for instance, so we have a 
more responsive shutdown. I'm also planing to delegate more discovery processes 
to JSR-330 (injection engine - more than one implementation exist today, so its 
look like that developers will have some choices if Geotk uses the standards 
annotations).

Regards,

     Martin