Hi Alessandro, I had a look at the code that throws the exception and it seems like a bug. I have raised a JIRA issue for this: https://jira.codehaus.org/browse/GEOT-4196. As a workaround, you have to duplicate the non-feature type mapping and give it a different mappingName. Thanks for reporting.
Rini -----Original Message----- From: Caradoc-Davies, Ben (CESRE, Kensington) Sent: Monday, 9 July 2012 9:13 AM To: alessandro marrone; [email protected]; Angreani, Rini (CESRE, Kensington) Subject: Re: [Geoserver-users] possible bug in app-schema module for non-feature elements Alessando, I think in this case you should not include the mapping but define it as a top-level type. This should work even if the type is not a feature type; it should be available for chaining but not via WFS. Rini, can you confirm? Kind regards, Ben. On 06/07/12 16:47, alessandro marrone wrote: > thank you for the quick answer > > maybe I did not explain well the problem, > the non-feature type is defined in only one way and it's used from two > (or more) different feature types > > > > Date: Fri, 6 Jul 2012 12:48:38 +0800 > > From: [email protected] > > To: [email protected] > > CC: [email protected] > > Subject: Re: [Geoserver-users] possible bug in app-schema module for > non-feature elements > > > > 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 <[email protected]> > > Software Engineer > > CSIRO Earth Science and Resource Engineering > > Australian Resources Research Centre > > > > -- Ben Caradoc-Davies <[email protected]> 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
