Andrea Aime wrote: > But quite frankly, this seems unnecessary too. In this JIRA > http://jira.codehaus.org/browse/GEOT-2385 > you state: > "When GeoServer invokes an OutputFormat, it has no access to the WFS > feature type name, only the name that can be determined from the > FeatureCollection.getSchema(), which is the content model type name" > > Reality is different, as you have full access to the Operation > even in the encoder, meaning this code (which I grabbed from > the GML3OutputFormat superclass): > > GetFeatureType request = (GetFeatureType) > OwsUtils.parameter(operation.getParameters(), > GetFeatureType.class); > > will give you full access to the parsed WFS request. > You just have to scan the list of Query and you get access to the > original type name requested by the user. There is a 1-1 correspondence > between the nth QueryType and the nth FeatureCollection (which I believe > it's mandated by the WFS spec).
Andrea, you are a champion. This looks to be several orders of magnitude less painful than any API change. I will try this. Many thanks, -- Ben Caradoc-Davies <[email protected]> Software Engineer, CSIRO Exploration and Mining Australian Resources Research Centre 26 Dick Perry Ave, Kensington WA 6151, Australia ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
