March 3, 2021
Hot Topics:

Enterprise Java Contract-First vs. Contract-Last Web Services

  • By Vlad Kofman
  • Send Email »
  • More Articles »

Example of XSD Schema for SOAP message

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
   <xsd:include schemaLocation="Master.xsd"/>
   <xsd:complexType name="ProductSchemaType">
         <xsd:element name="DataArea"
   <xsd:complexType name="ProductDataAreaType">
   <xsd:element ref="ns:Action"/>
   <xsd:element ref="ns:Product" minOccurs="0"
   <xsd:element name="Product" type="ns:ProductSchemaType"/>


In this article, I have shown you different ways to implement SOAP web services. The methods I have described involve either RPC or Document approaches, and can significantly differ in ROI and development and maintenance efforts. It will be up to the readers to decide which methodology is right for his project and what technologies they need to use.

It will be interesting to see what new improvements will appear in the area of the enterprise web services next and how current standards will evolve.

Special thanks go to Man Chan for his terrific insights into the Document-based web services!


About the Author

Vlad Kofman works on enterprise-scale projects for the major Wall Street firms. He has also worked on defense contracts for the U.S. government. His main interests are object-oriented programming methodologies, UI, and design patterns.

Page 3 of 3

This article was originally published on May 8, 2008

Enterprise Development Update

Don't miss an article. Subscribe to our newsletter below.

Thanks for your registration, follow us on our social networks to keep up-to-date