Kevin, please show us the mappings for this element and how you defined the new element.
Be sure to have the correct nesting of type and property type so that the GML encoding rule object/property/object/property... is observed otherwise the GeoTools Encoder will silently ignore your complex content. I suspect that avwx:aerodromeWxForecast should be defined as a wx:ForecastPropertyType. Kind regards, Ben. On 02/10/14 04:54, Weiss, Kevin wrote: > Ben, > Thanks for the reply. I modified the locally cached copy of the schema and > was able to bypass the "No top level element" error. I'm now getting WFS > responses that contain multiple avwx:aerodromeWxForecast elements...however > no matter what I try the aerodromeWxForecast elements are empty. (See > attached for an example snippet) The number of elements is correct (3 in the > attached example), but the sub-elements are not getting populated and no > error is generated. > The feature chain mapping appears to be correct and is included by the parent > mapping file. I can force it to generate an error by intentionally > misspelling one of the column names which results in an error listing the db > contents. In that error I can see it is correctly retrieving data from the > table, but it never results in a populated element. > I'm using feature chaining on a few other data types without issue and this > case doesn't appear to be any different configuration-wise. > > Any ideas on what I might try to resolve this would be greatly appreciated. > Thanks, > > Kevin M. Weiss > Software Engineer > HARRIS IT Services > > -----Original Message----- > From: Ben Caradoc-Davies [mailto:ben.caradoc-dav...@csiro.au] > Sent: Wednesday, October 01, 2014 2:06 AM > To: Weiss, Kevin; geoserver-users@lists.sourceforge.net > Subject: Re: [Geoserver-users] WXXM and app-schema plug-in > > Kevin, > > I checked with feature chaining expert Rini Angreani who confirmed "No > element, no mapping." > > There is an easy workaround: modify the schema in your app-schema-cache. > (The same trick will work with an OASIS Catalog but cache is easiest; I > recommend being lazy.) GeoServer app-schema will use the version in the cache > and never update it so your changes are safe. Caches are also portable and > can be deployed to other instances. If you change the definition in your > cache to be compatible with GeoServer app-schema, you can still refer to the > canonical schema location in your mapping files and it will be encoded as > such in responses. As long as your changes do not change the information > model, this is a complete, interoperable solution. The behaviour of schema > caching is designed to allow this workaround. > > For details on schema resolution, see: > http://docs.geoserver.org/latest/en/user/data/app-schema/app-schema-resolution.html > > Kind regards, > Ben. > > > On 01/10/14 02:24, Weiss, Kevin wrote: >> Hello all, >> >> I’m running into an issue attempting to map our DB contents to an >> avwx:TAF object as defined in the WXXM 1.1.1 schema. I believe the >> issue is that the WXXM schema defines a 0..n mapping of avwx:TAF to >> avwx:aerodromeWxForecast objects, but the avwx:aerodromeWxForecast >> element is defined within the SurfaceForecastReportType rather than as >> a top-level complexType. When I attempt to use feature chaining to >> create these sub-elements the result is: >> >> “NoSuchElementException: No top level element found in schemas: >> {http://www.eurocontrol.int/avwx/1.1}aerodromeWxForecast”. >> >> The WXXM schema in question can be found here >> <http://www.wxxm.aero/gallery/content/public/schema/1.1.1/avwx/icaoSurfaceForecastReport.xsd>. >> >> >> http://www.wxxm.aero/gallery/content/public/schema/1.1.1/avwx/icaoSurf >> aceForecastReport.xsd >> >> Seeing that these schemas are outside of my control is there any >> workaround I could try that doesn’t require modification of the schema >> itself? >> >> Thanks, >> >> *Kevin M. Weiss* >> >> Software Engineer >> >> *H**/A/**RRIS IT Services* >> >> >> >> ---------------------------------------------------------------------- >> -------- Meet PCI DSS 3.0 Compliance Requirements with EventLog >> Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI >> DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download >> White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with >> EventLog Analyzer >> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg. >> clktrk >> >> >> >> _______________________________________________ >> Geoserver-users mailing list >> Geoserver-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-users >> > > -- > Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineer CSIRO > Mineral Resources Flagship Australian Resources Research Centre > -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineer CSIRO Mineral Resources Flagship Australian Resources Research Centre ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
