HydraExpress provides an API for creating your own handlers. The classes in this API are implemented in the Web Services Library and are described in the HydraExpress Web Service Reference Guide. Table 9 describes the classes that are the most important for creating custom message handlers.
Figure 8 shows the relationship between the message handler SDK and the generated classes. Note that all of Web service-related classes generated by HydraExpress are essentially message handlers. The two handlers that appear by default in <serviceName>handlers.xml, MyServiceImp and MyServiceSkeleton, both derive (through intermediaries) from rwsf::MessageHandlerImp, as will your custom message handlers.
The file <servicecontextname>_handlers.xml is generated and initially contains a pointer to the service implementation and the SOAP message handler skeleton. Section 15.5 discusses using this file to configure and chain handlers. The file client-handlers.xml is also generated. In the request-response and one-way message patterns it supports only the logger handler. In the notification and solicit-response message patterns it is similar to <servicecontextname>_handlers.xml, with configuration elements for transport, request, response, and fault handlers. For information on the notification pattern, see Chapter 9, "Introduction to Message Patterns." For information on the solicit-response pattern, see Section 9.2.5, "The Solicit-Response Pattern."
To create your own handler, just derive directly from rwsf::MessageHandlerImp and add pointers to your handlers in <servicecontextname>_handlers.xml. For more information, see Section 15.4, "Creating Your Own Handlers."
©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.