Justin Deoliveira wrote: > Those of you watch the commit logs will notice I committed my changes > for GSIP 34 :). What this means is: > 1) the new data directory is in effect. So the first time you start up > geoserver with your current data directory it will be "morphed" as > outlined by the proposal.
What is the minimal configuration required to serve a single WFS feature type from a single data store? app-schema is configured by manually editing these test files. I wonder how your "morphing" handles relative paths? Examples: (1) the app-schema DataAccess url, which is the relative path from the catalog.xml to the app-schema configuration/mapping file <datastore namespace="gsml" enabled="true" id="MappedFeature"> <connectionParams> <parameter value="app-schema" name="dbtype"/> <parameter value="file:featureTypes/MappedFeatureUseCase2A/MappedFeatureUseCase2A.xml" name="url"/> </connectionParams> </datastore> (2) the relative paths in said configuration file to the OASIS catalog and profile schemas. <catalog>../../schemas/catalog.xml</catalog> and <targetTypes> <FeatureType> <schemaUri>../../profiles/MappedFeatureUseCase2A.xsd</schemaUri> </FeatureType> </targetTypes> I expect these will break. :~-( -- Ben Caradoc-Davies <[email protected]> Software Engineer, CSIRO Exploration and Mining Australian Resources Research Centre 26 Dick Perry Ave, Kensington WA 6151, Australia ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
