Gabriel Roldan wrote: > I've been working on setting up a prototype app-schema instance a couple > weeks ago but did it against the 1.6.x community-schema modules since > trunk wasn't ready for gml encoding yet. > Now, the schema I was targeting needed multiple levels of attribute > grouping for multiple nested complex values. That was not supported > since we only had "grouping" at the top most level of attribute mapping, > so I quickly hacked a new "GroupingFeatureIterator" that accounts for > that and added a "groupBy" config option to the general AttributeMapping. > So the question is if that capability is still unsupported on trunk and > if so if/how could I contribute back this enhancement to trunk. > If desired I can make a patch for your evaluation (besides, this > groupingfeatureiterator incarnation looks less cluttered than the > current one but would still need some work in order to get "user data" > values working, but I guess you're still trying to un-hack that as for > what complex atts with simple content respect?)
Gabriel, app-schema on trunk uses feature chaining to support multiple multivalued properties (I think these are what you describe). Rather than grouping, we have a separate view for each potentially multivalued nested complex type. These are treated as features for API purposes (even if they are not). From what I can tell, Rini has implemented grouping, which is required to represent many-to-many relationships even in feature chaining: https://www.seegrid.csiro.au/twiki/bin/view/Infosrvices/GeoserverFeatureChainingUserGuide Please take a look. We would be interested in your opinion of this approach. I am not sure if your new GroupingFeatureIterator can be used in trunk. Nonetheless, I am sure it would be of interest to Rini. The encoder implementation is now (mostly) working. It still has problems, including no XML attributes (ClientProperties), broken gml:description ("[" and "]" around the test) and some properties are missing. But the XML is well-formed and we have multiple multivalued properties. The four GeoTools/GeoServer patches needed to run GeoServer community/app-schema/app-schema-test AppSchemaGetFeatureTest are attached to the following issues: Honour feature descriptor type name in GML3EncodingUtils http://jira.codehaus.org/browse/GEOT-2442 Support encoding of multivalued properties for complex features in GML2EncodingUtils http://jira.codehaus.org/browse/GEOT-2443 Add SubstitutionGroupXSAnyTypeBinding to support encoding property type pattern http://jira.codehaus.org/browse/GEOT-2444 Enable encoding of application schema property type pattern in v1_1_0 WFSConfiguration http://jira.codehaus.org/browse/GEOS-2905 Kind regards, -- Ben Caradoc-Davies <[email protected]> Software Engineer, CSIRO Exploration and Mining Australian Resources Research Centre 26 Dick Perry Ave, Kensington WA 6151, Australia ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
