This section contains information relating to the Validation component.

IThe 'validator' component supports the concept of *validation* of information models, this through validators. This component is used to validate ebXML document (BPS, TPA, TPP, XMLSchema) after being read from storage into memory, possibly using the resolver component functionality. It is also used in a user editing environment where the user may get feedback when different constraints are violated.

Examples:

• A *warning* may be returned when an identifiers length is less than 3
  characters. A warning indicated that the model is *valid* but should be changed.
• An *error* may be returned when a statemachine contains no startstate.
  An error indicates that the information model is *invalid* and cannot be used.

A set of validators are grouped together to form a ValidationContext,a context may extend other contexts. The validators and contexts are currently dynamically configured through reading a XML configuration file.

Link to CVS directory

Core parts:

ModelCritic: encapsulates a single critic of some business object. The critic is graded as information , warning, error and fatal.

ModelCritics: list of critics, usually returned as a result of a validation.

ModelValidator: superclass for validators.

ModelValidatorContext: the context in which a validation is performed.

Screenshoots:

The following screenshot show a GUI (Swing) presentation of the result of a performed validation. The perticular validation a Collaboration Protocol Profile document validation. The last error is a missing referance to a transport specification.