Alexandre Gacon ha scritto:
Hi,
Hi... please keep the messages on the ml 
A fresh new install offers me all the classic coverage plugins.
But if I follow the instructions to install the native JAI,
http://docs.codehaus.org/display/GEOSDOC/Dealing+with+native+JAI
And particulary this line:
"Once you have installed JAI, if you want, you may unpack the Geosever WAR
file and remove the jai related files (this is the best cure for all
classloading issues): jai_core-x.y.z.jar, jai_imageio-x.y.jar and
jai_codec-x.y.z.jar."Then the plugins disappear from the page.
In fact, I installed the native JAI provided by Sun with the installer but
it seems that the jars don't have version numbers. In fact, they are named
jai_codec.jar and jai_core.jar.Do you think I should renammed then to be able to use the native JAI ?
Hum, no, they should not. Which version of the JAI have you installed, the one for jdk or the one for the jre? GeoServer uses the jdk to run.
In my jdk1.6.0_04\jre\lib\ext I do have, among the others:
clibwrapper_jiio.jar
jai_codec.jar
jai_core.jar
jai_imageio.jar
localedata.jar
mlibwrapper_jai.jar
and in jdk1.6.0_04\jre\bin:
clib_jiio.dll
clib_jiio_sse2.dll
clib_jiio_util.dll
mlib_image.dll
mlib_jai.dll
mlib_jai_mmx.dll
mlib_jai_util.dll
(if you're on linux you'll have a slightly different listing of
.so files)
With these in place the jai jars in geoserver should not even be
seen anymore because whatever is thrown into jdk/jre/lib/ext
is put in the classpath before the jars in GeoServer.
That is, unless your web container is playing tricks with the
classpath. What are you using?
Cheers
Andrea