Allesandro, the mappingName tag was introduced for this use case, to allow multiply-defined non-feature types to each have a unique internal name so chaining is unambiguous: http://docs.geoserver.org/latest/en/user/data/app-schema/feature-chaining.html#multiple-mappings-of-the-same-type http://docs.geoserver.org/latest/en/user/data/app-schema/mapping-file.html#typemappings-and-featuretypemapping
(Credit to Rini for both the implementation and detailed documentation.) Kind regards, Ben. On 05/07/12 20:50, alessandro marrone wrote: > Hello > I'm facing some problems using <includedTypes> tags for non-feature objects > > if I use it for one feature I have no problems, > but if I have two feature types that include the same non-feature type, > I obtain this messagge: > Error occurred getting features > Duplicate mappingName or targetElement across FeatureTypeMapping > instances detected. > They have to be unique, or app-schema doesn't know which one to get. > Please check your mapping file(s) with mappingName or targetElement of: > http://xml.fmi.fi/namespace/woml/core/2011/11/15:TimeInterpolation -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
