Hi, I'm trying to start again on WPS in GeoServer, and after some investigatin, I'm still stuck where I was stuck back in December: bridging the Sextante plugin API with our SPI subsystem.
The thread is here: http://n2.nabble.com/Problems-integrating-Sextante-with-GeoTools-SPI-td1959480.html#a1959480 To sum up, it's not possible to programmatically bridge the two API unless one creates a different ProcessFactory class for each of the Sextante algorithms. Now, I'm not really looking forward to write 200+ classes to import all the Sextante algorithms. The solution suggested in the thread was to make a factory that can bear multiple algorithms. I see two paths ahead: - change the whole ProcessFactory definition so that it returns a list of process names, and takes a name parameter in each call (api break) - create a new CompositeProcessFactory that is defined as: CompositeProcessFactory { Set<String> getProcessNames(); ProcessFactory getProcessFactory(String name); } The latter would be then registered in SPI, and the Processors class (which should really be named ProcessFinder for consistency with the other finders around) could inspect both registries, the one for single processes, and the composite one. Opinions? Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
