Hi all, I am looking at using the catalog api that was ported to geotools some time ago in GeoServer. Looking at the api I have some thoughts that I would appreciate feedback on.
1. Client properites for Service, and GeoResource handles. It would be nice to associate application specific information such as namespace prefixes, etc.. with a resource or service handle. 2. Mutability of metadata (*info) interfaces. Does it make sense to have these interfaces be mutable. Some of the metadata elements dont really make sense to be published by the service itself. An example would be publisher, or abstract. 3. Visitor Marching threw the catalog and testing each handle gets kind of tiresome. It would be nice to have a visitor to abstract a lot of this away. Feedback much appreciated. -Justin -- Justin Deoliveira The Open Planning Project [EMAIL PROTECTED] Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
