App-schema: defining multiple schemaURI results in invalid schemaLocation
-------------------------------------------------------------------------
Key: GEOS-4098
URL: http://jira.codehaus.org/browse/GEOS-4098
Project: GeoServer
Issue Type: Bug
Components: WFS
Reporter: Rini Angreani
Assignee: Justin Deoliveira
Fix For: 2.0.x, 2.1.x
Attachments: SISS-806-app-schema-test.patch, SISS-806-gt-app-schema.patch, SISS-806.patch
App-schema mapping file allows multiple schemaURI, for cases where the schemas needed don't know about each other's existence (are of different namespaces and don't import/include each other), but still related.
E.g. if the type in the first schema has an attribute of GeologicFeatureType, and the second schema extends GeologicFeatureType.
Therefore, I have updated the schemaLocations handling to include all schemaURI specified, for the getFeature output to be valid.
i.e. in GML3OutputFormat for getFeature header and also in FeatureTypeSchemaBuilder (for DescribeFeatureType).
Justin, please review my patch for xsd-gml3 module (SISS-806.patch).
The test changes are in app-schema-test (SISS-806-app-schema-test.patch).
It requires the changes in gt-app-schema to work (SISS-806-gt-app-schema.patch).
Many thanks
Rini
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira