Página... Architecture

Architecture of ISValidator

This page descibres the philosophy and architecture of development that is applied in ISValidator routines.

If you want to see commented examples of the routines, has the page of examples to it.

Philosophy of the routines

The philosophy whereupon has designed ISValidator turns surroundings to the information. Let think about an atomic information, like can be the name of a person that the user introduces in the system, by a web or console interface

On this information normally a series of processes is due to make: it must be model, be validated and processed, independent of if it is valid or no

Normally at the time of making the management of a certain information this is not to the only one that we must manage, usually are more information, as it can be the surname, the second name, etc...

Normally a certain information can undergo a validation by different restrictions, we put for example that to a name can be applied the restriction to be of certain lenght and not to contain numbers. They are two restrictions on an only one information

Also usually occurs the case that the restrictions that it has to fulfill a information are in favor conditional of other information. Let put for example the typical questionnaire in wich if it is answered an answer affirmatively it must answer a series o questions, not if it has been answered negatively there are to answer. In this case the restrictions that they have to fulfill these other questions vary according to the question that disciminates.

If the information to validate comes from an interaction with the user and this is not valid normally will have to let itself know to this for its correction.

Components of ISValidator

In order to medel this situation ISValidator routines are based on a series of components:

• Restrictions that are model as Constraints
• Atomic information that they are model as ConstraintContainers
• Assemblies of atomic informations that are model as MetaContainers
• Processes of information that are model like InValidConstraintProcessor and ValidConstraintProcessor

Restrictions

The restrictions to apply to a certain information are model using the Constraint interface and its corresponding implementations.

Each instance of a restriction is associate obligatorily to an one information (ConstraintContainer). Normally the restrictions provide the posibility of being used witout having to be associate to an information (ConstraintContainer) by means of the implememntation of a static method that makes the validation happening. This form to operate is not most habitual when several information are handled, but can be useful for validations of an one data.

These components are the ones in charge to make the function of described validation in the presentation

Atomic information

The atomic informations are model using the ConstraintContainer interface. This name come because it contain the restrictions.

One of the functions that makes it has the handling the flow of control between the different components that forms the routines

Each atomic information normally will be represented by only one ConstraintContainer

These components, along with the metacontainers are the ones in charge to make the function of model described in the presentation

Assemblies of atomic information

Los conjuntos de informaciones atómicas se modelizan mediante la interface MetaContainer, ya que la función que realizan es la de contener contenedores. Para obtener una lista de todos los MetaContainers actualmente desarrollados puede consultar la página de MetaContenedores.

Estos componentes son opcionales aunque normalmente facilitan el trabajo de manejar varias informaciones atómicas, al agruparlas.

Estos componentes, junto con los contenedores son los encargados de realizar la función de modelización descrita en la presentación

Procesos de la información

Los procesos de la información se modelizan mediante dos interfaces dependiendo de si la información es válida o por el contrario no lo es. Para procesar la información válida se utiliza la interface ValidConstraintProcesor y para la información inválida se utiliza la interface InValidConstraintProcessor. Para obtener una lista de todos los ValidConstraintProcessor actualmente desarrollados puede consultar la página de Procesadores Validos. Si quiere obtener la lista de los inválidos puede consultar la página de Procesadores Inválidos.

Estos componentes son totalmente opcionales, realizando la función de procesamiento descrita en la presentación