App-schema: id-less nested features cause NullPointerException
--------------------------------------------------------------
Key: GEOT-3461
URL: http://jira.codehaus.org/browse/GEOT-3461
Project: GeoTools
Issue Type: Bug
Components: data app-schema
Affects Versions: 2.7-RC2
Reporter: Rini Angreani
Assignee: Victor Tey
Fix For: 2.8-M1
When we have a nested feature that extends AbstractFeatureType, and the feature
doesn't have primary key and idExpression is not specified, it will cause
NullPointerException.
It doesn't happen for top level features because they would automatically
generate random ids as gml:id.
Nested features, however are treated as complex attribute, not Feature,
therefore the id generation doesn't happen.
It is valid to not have gml:id, since it's optional.
To fix this, add null checking in Gml3EncodingUtils, where it does
feature.getID().toString.
--
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
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
