Why does the existing code scan classloaders? I would say that only the context classloader should be used (unless that is null, then you can fallback to this.getClass().GetClassLoader()). In would expect that not using the context classloader would make the scanning fail in EE environments (like JBoss). As application servers can mess around with the classloader quite a bit, I would assume that any attempt to make sure it works in all environments is tricky to say the least.
Joachim On 05/16/2011 11:41 AM, Jan De Moerloose wrote: > Hi, > > as reported in http://jira.codehaus.org/browse/GEOT-2817, there is an > issue with the FactoryRegistry combined with GWT. I noticed that there > is an effort going on to replace the SPI mechanism with something more > extensible that would work on all environments. I will try to get > involved in that, but in the mean time i would like to know if there are > any objections against a patch that would force the context class loader > to be used in all circumstances where it is present ? > -- Joachim Van der Auwera Geosparc, supporting the Geomajas GIS community ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
