Hello all,
I would like to move the new catalog api from spike onto trunk. For
those not familiar check out:
http://www.geotools.org/display/GEOTOOLS/CatalogAPI
This involves two things:
1. Killing org.geotools.catalog.Catalog
2. Deciding how to organize the catalog modules
I dont really see a problem with the first. I killed it in my sandbox
and did a build and everything went ok.
I am sure not sure about the second. At present the catalog modules are
arranged as so:
catalog-api
catalog-wms
catalog-wfs
catalog-shp
With a seperate module for each type of service.
I see two possiblities:
1. It would be easy enough to make catalog-api a module, and everything
else plugins. However this will result in a significant increase in the
number of plugins.
2. Make the catalog-api a module, and merge all the other catalog
modules in with their corresponding data store plugin.
Any thoughts on how to proceed?
-Justin
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
