Service Chains Configuration File: handlers.xml
The configuration file <servicecontextname>_handlers.xml is generated as part of the server side components. It chains together the handlers for this service and contains initialization parameters. For more information on handlers, see Chapter 14, SOAP Message Handlers.
Following is an excerpt from dayofweek_handlers.xml:
<service name='DayOfWeekPortService'> 1
<request-handlers> 2
<handler name='http://localhost:8090/dayofweek/DayOfWeekSkeleton'/>
<service-endpoint name='http://localhost:8090/dayofweek/DayOfWeek'/> 3
//1 The attribute name identifies the name of the service, and maps from the serviceName attribute in web.xml. When the servlet identified in web.xml receives a message, it passes it to the DayofWeekPortService to handle.
//2 The request is passed to any transport handlers that might exist (none in this case) and then on to any bindings defined in the request-handlers element. (In this example, there is just one binding -- the SOAP message handle.) The request is then dispatched to the server implementation.
//3 The element service-endpoint identifies the service implementation and its location.
NOTE: The element transport-handlers should not be confused with the transport itself. An optional transport handler might add message encryption, compression, or special encoding. A transport handler manipulates the request before passing it to the request handlers, the response after any response handlers, and just before it is sent by the transport.