Examples of ValidationProcessor

• com.github.fge.jsonschema.processors.validation.ValidationProcessor
  Main validation processor
• com.sun.xml.internal.ws.api.policy.ValidationProcessor
  Provides methods for assertion validation. @author Fabian Ritzmann
• com.sun.xml.ws.api.policy.ValidationProcessor
  Provides methods for assertion validation. @author Fabian Ritzmann
• eu.maydu.gwt.validation.client.ValidationProcessor
  The ValidationProcessor is the core of the client side validation functionality. It is responsible for invoking the validations and the actions for the failed validators. It is also used to process the server side validations, if they are passed to the processServerErrors method. A default implementation is provided via the {@link DefaultValidationProcessor}. @author Anatol Mayen
• org.geotools.validation.ValidationProcessor
  ValidationProcessor Runs validation tests against Features and reports the outcome of the tests.

  The validation processor contains two main data structures. Each one is a HashMap of ArrayLists that hold Validations. The first one, featureLookup, holds per-feature validation tests (tests that operate on one feature at a time with no knowledge of any other features. The second one, integrityLookup, holds integrity validations (validations that span multiple features and/or multiple feature types).

  Each HashMap of validations is hashed with a key whose value is a FeatureTypeName. This key provides access to an ArrayList of validations that are to be performed on this FeatureTypeInfo.

  Validations are added via the two addValidation() methods.

  The validations are run when runFeatureTests() and runIntegrityTests() are called. It is recommended that the user call runFeatureTests() before runIntegrityTests() as it is usually the case that integrity tests are much more time consuming. If a Feature is incorrect, it can probably be detected early on, and quickly, in the feature validation tests.

  For validations that are performed on every FeatureTypeInfo, a value called ANYTYPENAME has been created and can be stored in the validationLookup tables if a validation specifies that it is run against all FeatureTypes. The value that causes a validation to be run against all FeatureTypes is null. Or Validation.ALL

  Results of the validation tests are handled using a Visitor pattern. This visitor is a ValidationResults object that is passed into the runFeatureTests() and runIntegrityTests() methods. Each individual validation will record error messages in the ValidationResults visitor.

  Example Use:

   ValidationProcessor processor = new ValidationProcessor();
   processor.addValidation(FeatureValidation1);
   processor.addValidation(FeatureValidation2);
   processor.addValidation(IntegrityValidation1);
   processor.addValidation(FeatureValidation3);
   
   processor.runFeatureTests(FeatureTypeInfo, Feature, ValidationResults);
   processor.runIntegrityTests(layers, Envelope, ValidationResults);
   

  @author bowens, Refractions Research, Inc. @author $Author: jive $ (last modification) @source $URL$ @version $Id$
• org.locationtech.udig.validation.ValidationProcessor
  Subclass for the geotools ValidationProcessor, with added methods which allow for tree navigation, etc. For the most part, this adds more baggage to the class so the Validation Dialog can get information out of it.

  @author chorner @since 1.0.1 @see org.geotools.validation.ValidationProcessor
• org.openfaces.component.validation.ValidationProcessor
  @author Vladimir Korenev

Examples of org.openfaces.component.validation.ValidationProcessor