Taking this to geoserver-devel; Ben if you have people that would like to follow this discussion they can sign up.
> A different collection interface would be preferred, no need to add > extra xml specific concerns in all the use cases that do not require > it. > > 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): Thanks Andrea that is a much better solution; I would prefer not to mess with the FeatureCollection interface; indeed we are trying to reduce its scope to something Justin can stand. Jody ------------------------------------------------------------------------------ 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
