Hello! If an auto-commit transaction is used in ShapeFileDatastore then during any features modification FeatureListener[s] do not get any notifications. Only if the transaction is non-auto-commit then DiffFeatureWriter and TransactionStateDiff contains the code to notify listeners.
It causes UDIG, for example, not to re-render the layer where features were modified/added/removed (in case of shapefile). Am I right with this suspicion? Seems the notification mechanism is spread among classes.. Isn't implementation of FeatureStore is the right place to have notification mechanism and way to turn on/off, batch notifications, etc. ? No matter what is a nature of datastore, the FeatureStore implementation may collect necessary information from datastore specific implementation classes but send these notifications in a centralized way. I did not look into JIRA yet, so may be this is a known issue. Vitali Diatchkov. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
