Databases Reference
In-Depth Information
Summary
In this chapter, we've looked at how we can implement validation within an
individual service through a combination of XSD validation, Schematron, and
Business Rules.
Ideally we should use XSD validation to check the overall sanity of the data, but in
order to provide a greater level of flexibility, we then extract the business-specific
validation into a separate component such as Schematron. This gives us more
flexibility to change the validation for a component without the need to redeploy
a new version of it.
In situations where Schematron can't provide the required validation, we've
looked at how we can use Business Rules to build this into the underlying service
implementation, again giving us the flexibility to change the validation without
having to redeploy the service.
Finally, we've looked at some of the issues and potential strategies for validation
when combing multiple services, while there are no simple solutions. By at least
having an idea of the issues, we are able to take these into account in the design of
our overall solution.
