TransactionStateDiff.NULL feature tripping up ShapefileRenderer due to
PropertyAccessor error
---------------------------------------------------------------------------------------------
Key: GEOT-1596
URL: http://jira.codehaus.org/browse/GEOT-1596
Project: GeoTools
Issue Type: Bug
Components: core filter, ext shapefilerender
Reporter: Jody Garnett
Assignee: Jody Garnett
A cascade of changes here:
1. DirectPropertyAccessor could not handle a Property with out a name (shades
of Oscar Wilde), so getDefaultGeometry on a TransactionStateDiff.NULL was a NPE
2. Fixing that caused IntersectImpl superclass to return null for
getLeftGeometry(), but since it only checked that the right hand side was non
null (rather than both) we had another NPE
3. ShapefileRenderer did not have try/catch/safety in the processTransaction
for loop
The bug was found while editing with uDig; as far as I know the first time the
property accessor stuff has been used on a transaction state diff? I have added
a bunch of toString methods to the suspects involved in this bug
(TransactionStateDiff.NULL) for example; I suspect that a "SimpleFeatureNull"
class is a more generally useful construct - that could be used to represent
deleted rows in a shapefile for example.
--
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 email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
