Examples of ValidationManager

com.sun.enterprise.tools.common.validation.ValidationManager
{@link ValidationManager} is an object that provides Validation functionality,through its validate( ) function. {@link ValidationManagerFactory} creates {@link ValidationManager} based on the Validation File. Validation File specifies Validation rules i.e. which Constraints to apply to which elements. Objects are validated by applying specified Constraints to its elements. Validation file is xml file based on validation.dtd. If no Validation File is specified, ValidationManagerFactory returns default ValidationManager. Default ValidationManager is based on default Validation File. Default Validation File defines Constraints for 8.0 Sun DTDs.
Validations are performed, recursively on the given Object. Two types of Validations are perfomed, Structural validations and Specified validations. Structural validations are expressed through {@link CardinalConstraint}. CardinalConstraint is an implicit Constraint. Its always applied to each of the element; you dont need to specify it explicitly. Whereas , other Constaints need to be explicitly specified for each element you wanted to apply it to. Constraints to be applied are specified through Validation File. You can also define, your own custom Constraints and apply them to any elements. When you define your own Constraints, you need to provide information about them to the framework. This information is provided through Constraints File. Constraints File is xml file, based on constraints.dtd. Constraints File to use is specified through system property constraints.file. You can override Constraints provided by framework , by providing your own. @see Constraint @see CardinalConstraint @see Validatee @see ValidationManagerFactory @author Rajeshwar Patil @version %I%, %G%
com.sun.org.apache.xerces.internal.impl.validation.ValidationManager
ValidationManager is a coordinator property for validators in the pipeline. Each validator must know how to interact with this property. Validators are not required to know what kind of other validators present in the pipeline, but should understand that there are others and that some coordination is required. @xerces.internal @author Elena Litani, IBM @version $Id: ValidationManager.java,v 1.2.6.1 2005/09/06 11:49:43 neerajbj Exp $
mf.org.apache.xerces.impl.validation.ValidationManager
ValidationManager is a coordinator property for validators in the pipeline. Each validator must know how to interact with this property. Validators are not required to know what kind of other validators present in the pipeline, but should understand that there are others and that some coordination is required. @xerces.internal @author Elena Litani, IBM @version $Id: ValidationManager.java 606491 2007-12-22 21:00:53Z mrglavas $
org.apache.xerces.impl.validation.ValidationManager
ValidationManager is a coordinator property for validators in the pipeline. Each validator must know how to interact with this property. Validators are not required to know what kind of other validators present in the pipeline, but should understand that there are others and that some coordination is required. @author Elena Litani, IBM @version $Id: ValidationManager.java,v 1.7 2002/12/11 16:14:31 elena Exp $

Examples of org.apache.xerces.impl.validation.ValidationManager

        addComponent(fDTDValidator);


        fDatatypeValidatorFactory = DTDDVFactory.getInstance();
    fProperties.put(DATATYPE_VALIDATOR_FACTORY, fDatatypeValidatorFactory);


        fValidationManager = new ValidationManager();
    fProperties.put(VALIDATION_MANAGER, fValidationManager);
        
        fVersionDetector = new XMLVersionDetector();
        
        // add message formatters

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.