Putting validation in the underlying service
So far we have looked at using XML Schema and Schematron to put validation either in the service contract or the Mediator layer in order to provide initial validation of a service invocation, before we actually invoke the underlying service. This provides a number of benefits, including:
- Simplifies the development of validation within the actual service, as it can now rely on the fact that it is receiving relatively sensible data.
- Allows us to implement a more generic service, as business-specific validation can be provided at a higher level within the service. This makes the service more reusable, as it can be used in multiple scenarios, each with different validation requirements.
- Makes changes easier ...