schemaURI ordering in app-schema mapping file shouldn't matter
--------------------------------------------------------------
Key: GEOT-3262
URL: http://jira.codehaus.org/browse/GEOT-3262
Project: GeoTools
Issue Type: Bug
Components: data app-schema
Affects Versions: 2.0.0
Reporter: Rini Angreani
Assignee: Rini Angreani
In app-schema mapping file, you can specify > 1 schemaURI if multiple schemas
are required for the feature type. In most cases, you only need 1 schema
because the schemas are usually indirectly linked (imported/included by the
imports/includes etc.)
However, this is still a valid scenario, e.g. when an attribute is of type
xs:anyType (therefore can have anything in it), and the mapped attribute is of
a type unknown to the top level feature type. Therefore you need to specify
both the top level schema, and the unknown type schema.
At the moment, if you specify the schemaURI in the wrong order, the attribute
won't be mapped. It is because the containing type wouldn't know about the
nested type (in the other schema), unless the nested type schema is specified
first (therefore already exists in the schema registry when the containing
schema is parsed).
What needs to be done is to update the relevant schemas in the schema registry
when a new schema is registered. I don't know how to do this efficiently yet.
--
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
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
