When you create your message model, it is important that
it is internally consistent.
To assist with this, whenever you save a message model schema file or message definition file,
it is validated as follows:
- Logical validation
- This validation ensures that the logical model is correct. For
message definition files, this involves ensuring that the rules of
XML Schema have been correctly followed.
- Physical validation
- This validation ensures that any physical properties that you
have specified for your model have been correctly populated and are
consistent. There is a set of checks for each of the MRM domain physical
formats - CWF, XML, and TDS - and for
DFDL.
After model validation has taken place, any errors or
warnings are shown in the task list. Double clicking a task list entry
opens the file and positions the editor at the object in error. Organize
the task list so that errors are shown before warnings. In this way,
errors are not hidden. The task list provides a comprehensive filtering
capability if you want to hide low priority warnings, or warnings
that you are know about and are comfortable with.
The deployment of a message model in a BAR file is prevented if any errors are present. The presence
of warnings alone does not prevent deployment, but high priority warnings
must be reviewed because a model that generates such warnings might
be incomplete.
Where task list warnings or errors occur, these are listed in the
Problems view of the Integration Development
perspective.
While a majority of these require you to manually investigate and
resolve them, a number of warnings and errors that meet specific criteria
can be repaired by using a quick fix process.