![]() ![]() See Section 6.3.2, "The Generated Data Types." ![]() Based on the zipcode, the server return an XML WeatherSummary element for the location specified by the zipcode.Ī WeatherSummary element is a complex type defined by an embedded XML Schema in the types element of the WSDL file. The message getSummaryResponse contains one part, a weatherData object of type wsx:WeatherSummary. The client request thus provides a zipcode to the server. The message getSummary contains one part, a zipcode of type xsd:string. The contents of these messages are then defined in the WSDL's message element: The operation getSummary contains an input message getSummary, which is the client request, and an output message getSummaryResponse, which is the server response. In dl, the request-response operation is defined by the getSummary operation: Figure 1: The Request-response message pattern The request-response operation includes one input element, which is the client's request to the server, followed by one output element, which is the server's response back to the client. This operation has been left out for the sake of simplicity. To complete this scenario, there should be another request-response operation that allows a zip code location to either subscribe or unsubscribe from the notification service, receiving a confirmation message in reply. Participating zip code locations send updated weather data to the service when local conditions change, using the one-way operation.Ĭlients can subscribe to receive notification of changed conditions through the notification operation.įinally, the service periodically polls the client to confirm that the client wishes to continue receiving notifications, through the solicit-response operation. The Weather Summary service represents a centralized provider of weather condition data for some number of zip code locations in some area.Ī client, or individual, requests weather data based on a zip code, and the service provides it, through the request-response operation. 9.2.1 Weather Summary Service Description It also includes a brief discussion on synchronous and asynchronous behavior as it relates to message patterns. ![]() This section discusses each message pattern, with an introduction to the dl that is used for illustration. Given the definition of the input and output messages for the operation in the WSDL file, HydraExpress generates the appropriate code for all four message patterns. The W3C WSDL Specification defines four message patterns to support four types of operations: Rogue Wave web site: Home Page | Main Documentation. HydraExpress Web Service Development Guide ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |