Allow feature chaining to use a non-schema field as foreign key
---------------------------------------------------------------
Key: GEOT-2545
URL: http://jira.codehaus.org/browse/GEOT-2545
Project: GeoTools
Issue Type: New Feature
Components: core feature
Reporter: Rini Angreani
Fix For: 2.6-M2
Attachments: SISS_349_GT.patch
At the moment, feature chaining uses real attributes in the nested type to be
referred by the parent type. If there is no real attribute available, gml:name
is to be used (despite not existing in the schema, gml:name was specially
handled). This is because gml:name is a multi-valued property, so we can have
multiple instances of gml:name as foreign keys to different parent types. A
codespace could be used to clarify the purpose of gml:name as foreign key, eg:
<gml:name
codeSpace="urn:cgi:classifierScheme:GSV:MappedFeatureReference">gu.25678</gml:name>
However, it is technically wrong to have these foreign keys appearing as fake
gml:name properties, because it'd confuse the users with real gml:name
properties.
It was suggested to use fake non-schema field to hold these foreign keys
instead, so they don't appear in the output (encoder would filter them out).
The only changes in core code are in: FeatureTypeImpl and
FeatureTypeFactoryImpl.
--
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
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
