Apache Axis2's local transport implementation is used to make fast, in-VM service calls and transfer data within proxy services. The transport does not have a receiver implementation. The following class implements the sender API:
Note: If you need to use local transport with callout mediator, you do not need to perform configuration mentioned in this section as callout mediator requires blocking local transport which is configured by default in WSO2 ESB distribution.
To use this transport, configure an endpoint with the
local:// prefix. For example, to make an in-VM call to the HelloService, use
local://services/HelloService. Note that the local transport cannot be used to send REST API calls, which require the HTTP/S transports.
Configuring the Local Transport
By default, WSO2 ESB provides CarbonLocalTransportSender and CarbonLocalTransportReceiver, which are used for internal communication among Carbon components and are not suitable for ESB service invocation. To enable the local transport for service invocation, follow these steps.
1. In the carbon.xml file at location
<ESB_HOME>/repository/conf, an endpoint is available as follows by default.
Replace it with
2. In the axis2.xml file at location <PRODUCT_HOME>/repository/conf/axis2/axis2.xml, there is a transport sender and receiver named 'local' specified as follows in two different places:
Remove both these lines and add following line.
For more information about transports, see Working with Transports.