Thanks, When I sended the example, I simplified this. The target attribute was : <targetAttribute>timeSlice/AirspaceTimeSlice/geometryComponent/AirspaceGeometryComponent/theAirspaceVolume</targetAttribute> I updated the local XSD to set theAirspaceVolume at the top of the Airspace, to see if there where the same problem. And there is the same problem.
If I set targetAttribute like this : <targetAttribute>timeSlice/AirspaceTimeSlice/geometryComponent/AirspaceGeometryComponent/theAirspaceVolume/AirspaceVolume</targetAttribute> I get empty AirspaceVolume tags when I have single volume,and when there is multiple volumes, I get my strange string inside the volume tag. So that mean that the encoder doens't understand how to decode multiple AirspaceVolume inside theAirspaceVolume tag ? How can I help the encoder to understand this ? - Editing XSD? - Create another intermediate Complex type (to describe theAirspaceVolume) ? JcA > On 22/10/15 01:49, Stefano Costa wrote: >> I had a quick look at AIXM 5.1 ( >> http://www.aixm.aero/gallery/content/public/schema/5.1/AIXM_Features.xsd), >> but the Airspace type defined there doesn't have any theAirspaceVolume >> property. > > Yes, in this schema, theAirspaceVolume is a property only of > AirspaceGeometryComponentType. > > JcA, you use > <targetElement>aixm:Airspace</targetElement> > [...] > <targetAttribute>aixm:theAirspaceVolume</targetAttribute> > [...] > <targetAttributeNode>aixm:AirspaceVolumePropertyType</targetAttributeNode> > to override the type information in the schema. If your mappings > conform the the AIXM schema, targetAttributeNode should not be > required. Your override does not work for multiple values so the > Encoder falls back to using a string representation of the internal > Java objects. This is not what you want. For a single AirspaceVolume, > the mapping appears to work, but the WFS response does not conform to > the AIXM 5.1 schema and is schema-invalid. Even if what you are trying > to do worked for multiple values, it would be schema-invalid. > > In the AIXM 5.1 schema, you can map AirspaceVolume nested inside > AirSpace/timeSlice like this XPath: > > AirSpace/timeSlice/AirspaceTimeSlice/geometryComponent/AirspaceGeometryComponent/theAirspaceVolume/AirspaceVolume > > I think you are missing several levels of nesting. > > Kind regards, ------------------------------------------------------------------------------ _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
