The W3C standards for Web services allow for more than one interpretation,
and the WS-I (Web services Interoperability Organization) introduced a separate
standard called the Basic Profile to tighten up their use. For example, the
WS-I Basic Profile does not allow the use of SOAP encoding, even though this
is often seen in practice.
The WS-I Validator can be used to check your WSDL definitions against the
Basic Profile. The validator can be run either:
- manually against a specific .wsdl resource in the workbench. This will
allow you to investigate and fix any WS-I compliance problems. Any validation
issues are displayed as task list errors and warnings. The behavior of the
validator can be controlled under .
- automatically on importing a WSDL definition (by using the WSDL Importer
wizard or the mqsicreatemsgdefsfromwsdl command)
or WSDL generation (by the WSDL Generator wizard). In this case errors are
displayed and also written to a report file.
You are able to set a validation
failure action to control the outcome of the validation as follows:
- ignore
- Any warnings from the WS-I validator will be written to the log file as
informational. The user is unaware of the messages unless they view the log
file. The user will be able to continue with the process.
- warn
- Any warnings from the WS-I validator will be written to the log file as
warnings. Any messages that generate a warning will be highlighted with yellow
symbols on the next panel of the wizard and the user will be able to continue
with the process.
- fail
- Any warnings from the WS-I validator will be written to the log file as
errors. Any messages that generate an error will be highlighted with red symbols
on the next panel of the wizard and the user will not be able to continue
with the process until the errors in the original WSDL definition are corrected
and it is revalidated.
You have to set the failure action to warn or ignore if
you want to use features which are not WS-I compliant such as SOAP encoding.