Hi Luca, youre wellcome! > The validators are planned to be used for *deriving* new geometries > from existing ones, and not only for validation. Probably they aren't > enough for an editing tool.
This is why you must throw an event. When the validator detects that rule is not passed, throw an event, and some rulesListener instances must do some process (derive new geometries, save an entry in a log registry of wrong geometries with topologic errors, etc.) > > If these topology rules dont verify, it would throw some events, and > > some listeners would process it. > This is very interesting. I think this model can fit the Validation > model so we can make both the interfaces work together. > > Cheers > > Sig > > Best regards! -- Alvaro Zabala Ordóñez Miembro fundador de AGIL Asociación para la promoción del GIS Libre www.agiles.org Funcionario del Cuerpo de Gestión de Sistemas e Informática de la Administración General del Estado. Confederación Hidrográfica del Guadalquivir. Teléfono: 954939523 Plaza de España, sector II. SEVILLA ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
