9.1 Overview
HydraExpress supports the four message patterns defined by the W3C WSDL Specification. These are:
One-way. The service receives a message from the client, and the client expects no response. Characterized by a single input element.
Request-response. The service receives a message from the client and sends a response. Characterized by one input element, followed by one output element.
Solicit-response. The service initiates a message to the client and receives a response from the client. Characterized by an output element followed by an input element.
Notification. The service initiates a message to the client, and expects no response. Characterized by a single output element.
This chapter introduces how to implement these four patterns in HydraExpress, using the shipped example WeatherSummary in the <installdir>\tutorials\webservices\WeatherSummary directory. The WeatherSummary example also demonstrates how HydraExpress handles complex types and how to autoconfigure a listener.
The pattern request-response is most commonly used in Web services, and is illustrated further in most examples in this book. See Chapter 7 and Chapter 8, as well as the chapters in Part IV, "Extending your Applications."
The patterns notification and one-way are discussed in more detail in Chapter 10, "Implementing One Way and Notification Messages." This chapter uses another shipped example that illustrates how to implement one-way and notification using HydraExpress's generated asynchronous methods.
The pattern solicit-response is comparable to the request-response pattern, except that the request is initiated by the server and the response is sent from the client. HydraExpress does not include an additional shipped example to illustrate this pattern, as its behavior is similar to request-response, and it uses the same architecture already described in the notification examples.
©2004-2007 Copyright Quovadx, Inc. All Rights Reserved.
Quovadx and Rogue Wave are registered trademarks of Quovadx, Inc. in the United States and other countries. All other trademarks are the property of their respective owners.
Contact Rogue Wave about documentation or support issues.