Andrea Aime wrote: > But isn't the namespace a publishing property, and > so something that should be set at the layer > level?
Some feature types get their namespaces glued on at publishing time. Some have their namespace as an intrinsic property; for example, app-schema feature types. You think you have problems: a DataAccess can provide feature types with qualified names in different namespaces. See DataAccess: "List<Name> getNames()". Given that a workspace and thus data store are named by the namespace prefix, if you want multiple namespaces from a single DataAccess, you are stuffed. For example, I can create a single DataAccess that returns a gsml:MappedFeature and a sa:SamplingPoint. In which workspace can this live? The workaround is to Not Do That Then, and instead proliferate DataAccesses, one per feature type. The catalog implementation prevents a legitimate use of the DataAccess API. See GEOS-3042. -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineer, CSIRO Exploration and Mining Australian Resources Research Centre 26 Dick Perry Ave, Kensington WA 6151, Australia ------------------------------------------------------------------------------ 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 _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
