Hi Ben, Many thanks! I discovered that I had to make some additional changes to the mapping file on top of the spelling correction ( setting Expose primary keys = true and changing the names of the target attributes under the type mappings ), but I finally have the town names coming through in the WFS request! We use XMLSpy as our validating XML Editor - however I had only used it to validate our GML application schema, it didn't occur to me that I could also use it to validate our mapping file!
Thanks again for your assistance, I will most likely be in touch again once I attempt some more complicated mappings :-) Best Regards, Ryan -----Original Message----- From: Ben Caradoc-Davies [mailto:[email protected]] Sent: 12 June 2013 03:20 To: Ryan Moody Cc: [email protected]; Ian Turton; Neil Kirk Subject: Re: [Geoserver-users] App-Schema Publish Layer Exception Found it. I pasted the entirety of your original mapping file into a validating XML editor (Eclipse JEE) with AppSchemaDataAccess.xsd in the same directory. Your mapping file is schema-invalid because of a misspelled element: <AttributeMappings> should be <attributeMappings> Because the mapping file parser is nonvalidating and only looks for child elements of <attributeMappings> and finds none, your mapping is ignored, resulting in a lack of content. I strongly recommend the use of a validating XML editor for correctness and helpful documentation and completion suggestions when editing. Kind regards, Ben. On 11/06/13 17:41, Ben Caradoc-Davies wrote: > Still thinking ... -- Ben Caradoc-Davies <[email protected]> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
