> At the moment, we have an AppSchemaDataAccessRegistry. When we understand the > Repository API, we might use it.
Sigh! And if we work together it will meet your needs :-) > Because feature chaining *requires* collaboration between DataAccess > instances in different namespaces, and because GeoServer *requires* the > workspace name to be equal to the namespace prefix (GEOS-3042), > cross-workspace communication is *required* for Christian's code to be > useful for feature chaining. Okay that explains the difficulty I had with the use of Christian's code referring to workspace. It really is just that the DataStore has a two part name - the first part indicating the "workspace" and the second indicating which DataStore. For today I just need things to compile; if anyone has a copy of GeoServer 1.7 checked out it could save me some trouble. Jody ------------------------------------------------------------------------------ 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
