Hello, I discovered an issue with JAI-ext that concerns both geotools and geoserver.
Currently I noticed that the JAIExt.initJAIEXT method (the initialisation of jai-ext) is called from a static block in geotools: https://github.com/geotools/geotools/blob/master/modules/library/coverage/src/main/java/org/geotools/image/ImageWorker.java#L182 However, in Geoserver, the following line potentially wipes clean all jai-ext operations by assuming a regular JAI registry is needed : https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/GeoserverInitStartupListener.java#L123 In GeoServer, the GeoserverInitStartupListener is apparently called by the web context before the static clause. So there is no problem. However, I believe this is just a fluke, there is absolutely no guarantee that it happens in that order. We currently are working on a project that is built on top of geoserver where the two things happen in the opposite order. In this project, the JAI-EXT configuration is wiped clean. And we needed a hack to explicitly reinitialise JAI-ext a second time. I do think that this is a bit of dodgy situation in general. Regards, Niels ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/xeonphi _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
