Today, developers are beginning to develop more sophisticated Web services, exchanging complex XML documents rather than simple parameter types. As this shift takes place, development teams begin to grapple with different approaches to designing these web services interfaces. Luckily, there are a number of best practices available for designing web services with XML Schemas and WSDL.
For example:
Using a modular schema design can maximize reuse of your Web services components, and can also simplify the process to map your interface to back-end implementation.
The proper use of namespaces can simplify references to XML data types. They can also be used as a mechanism to enforce Web services versioning.
The design should leverage the functionality of both XML Schema import and WSDL import. This feature can provide a great amount of reusability across message types and data elements.
Finally, proper design techniques should carefully consider impacts on interoperability. Not all platforms support the same XML Schema types and structures.
Through the use of these techniques, you will be able to achieve a higher degree of portability of your Web services, as well as realizing improved reusability and interoperability between a broader collection of Web services platforms.
In this session, Chris will draw on a number of XML-Journal and Web Services Journal articles published in 2003, including:
About Chris Peltz Chris Peltz is a senior architect within HP's
Developer Resources Organization (http://devresource.hp.com), providing technical and architectural consulting to enterprise customers in the areas of J2EE, Web services, and
application management.