Thanks Ben Those samples helped me get it working for "simple" complex features - but I'm stuck with the chaining side of things.
In my original example I said I have two tables in the database - and I was imagining that I would have two features in the output, however I just read a previous post you made to someone regarding feature chaining and suggested they create a view in the database to return the parent feature and all child records in a 1:many join view. Is this the correct way to perform feature chaining? Ie. does that mapping occur in the geoserver app schema module, rather than having it perform two independent object queries and join them? Shaw On 04/03/2011, at 14:38 , Ben Caradoc-Davies wrote: > On 04/03/11 12:18, Shaw Innes wrote: >> I'd be keen to have a look at the example you mention - even if it's more >> comlpex than I require it might give me some hints. > > Have a look at the documentation for the DataReferenceSet: > https://www.seegrid.csiro.au/wiki/bin/view/Infosrvices/DataReferenceSet > > The latest data is in this jar file (a JAR file is just a ZIP): > http://download.osgeo.org/webdav/geotools/org/geotools/data/refdataset-1.0/1.0.4/refdataset-1.0-1.0.4.jar > > The mappings are here: > https://svn.codehaus.org/geoserver/trunk/src/extension/app-schema/app-schema-test/src/test/resources/test-data/DataReferenceData/ > > To get them to work you will need to use properties files or just modify them > them get connections to work. You will also need the other files like > featuretype (I thing these are created dynamically at test time by Victor's > test harness). > >> One further question. Do I require a feature/featuretype.xml definition >> for PostIGIS based complex features? (I noticed in the "example" workspace >> checked out from the svn from the documentation that it has a subdirectory >> with a featuretype.xml also) > > This is only sufficient boilerplate to trick the GeoServer catalog into > loading your app-schema datastore and dispatching requests to it. In practice > it is not used much. It is required by GeoServer, because GeoServer would > expect it for simple features it created itself. Omitting this will cause > things to break. > > Kind regards, > > -- > Ben Caradoc-Davies <[email protected]> > Software Engineering Team Leader > CSIRO Earth Science and Resource Engineering > Australian Resources Research Centre ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
