As noted above, any object loaded into the Agent at startup is available to your service implementation at runtime. This includes all transports and message handlers configured in transports.xml, client-transports.xml, <servicecontextname>_handlers.xml, and client-handlers.xml. Your service, for example, might need to send a response via HTTP or HTTPS, depending on user preference. Implementing such a flexible transport policy is straightforward, requiring only that the needed transports have been configured. It is also possible to selectively add to the message handler chain any message handler configured in <servicecontextname>_handlers.xml. For more information on runtime switching, see Chapter 14, SOAP Message Handlers.