complex features can't handle null database values
--------------------------------------------------

                 Key: GEOT-2976
                 URL: http://jira.codehaus.org/browse/GEOT-2976
             Project: GeoTools
          Issue Type: Bug
          Components: core filter
    Affects Versions: 2.0.0
            Reporter: Rini Angreani
            Assignee: Rini Angreani
             Fix For: 2.7-M0


When complex feature encounters a null database value, it seems to get the 
wrong accessor (XPathPropertyAccessor) instead of SimpleFeaturePropertyAccessor.
This results in the output being encoded incorrectly from the feature 
containing null value to the last one(since the accessor is cached, so once it 
gets XPathPropertyAccessor, it will always use it for the next features).

Example:
 
<gsml:mineralName 
xlink:href="http://resource.nvcl.au/classifier/auscope/tsa/6.1/mineral/SimpleFeatureImpl.Attribute:
 CLASSTEXT<CLASSTEXT id=LOGDATA10M.fid--5710a6a2_125b91b4e25_-7fe8>=Sulfate" />
 
whereas, this is what we want:
 
<gsml:mineralName 
xlink:href="http://resource.nvcl.au/classifier/auscope/tsa/6.1/mineral/Sulfate"; 
/>

We also can't check for null values to avoid this. Using isNull() function 
doesn't work, since it returns null value wrapped in an xpath, so the function 
doesn't think it's null. This function is also needed for some of our use cases 
(to determine what's encoded, based on the value of the attribute). 

So the workaround is to replace null values with string representations, but it 
won't be convenient for large databases, and would always come up for new 
clients. 

-- 
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

        

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to