The transport receiver implementation of the HTTP transport is available in the Carbon core component. The transport sender implementation comes from the Apache Axis2 transport moduleTomcat http connector. This transport is shipped with WSO2 Carbon and all WSO2 Carbon-based products, which use this transport as the default transport, except WSO2 ESB. The two classes which implement the listener and sender APIs are org.wso2.carbon.core.transports.http.HttpTransportListener and org.apache.axis2.transport.http.CommonsHTTPTransportSender respectivelyBy default, we use non-blocking Tomcat Java connector org.apache.coyote.http11.Http11NioProtocol.
| Info |
|---|
|
- This is a non-blocking HTTP transport implementation, meaning which means that I/O the threads do not get blocked while received messages are processed completely by the underlying Axis2 engine.
- Although the Although the
axis2.xml file contains configurations for HTTP/S transports by default, they are not used by WSO2 products. Instead, the products use the HTTP/S transport configurations in Tomcat-level; therefore, changing the HTTP/S configurations in the axis2.xml file has no effect.
|
| Info |
|---|
|
In the transport parameter tables, the literals displayed in italic mode italics under the "Possible Values" column should be considered as fixed literal constant values. Those values can be directly put in into the transport configurations. |
...