This documentation is for WSO2 Complex Event Processor 2.0.0. View documentation for the latest release.

Skip to end of metadata
  • Created by Former user, last modified by Former user on Dec 12, 2012
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

Apache Axis2's local transport implementation is used to make internal service calls and transfer data within the Axis2 instance. The following class implements the sender API:

  • org.apache.axis2.transport.local.LocalTransportSender

The transport does not have a receiver implementation as of now.

It provides an opportunity for fast in-VM service call.

Note

To use this transport, configure an endpoints with the local:// prefix. For example, to make an in-VM call to the HelloService, use local://HelloService .

Configuring a Local Transport with WSO2 Products

Shown below is how to configure a local transport with any WSO2 Carbon-based product.

1. In the carbon.xml file at location <PRODUCT_HOME>/repository/conf, an endpoint is available as follows by default.

<ServerURL>local:/${carbon.context}/services/</ServerURL>

2. In the axis2.xml file at location <PRODUCT_HOME>/repository/conf/axis2, there is a transport sender named 'local' specified as follows:

<transportSender name="local" class="org.apache.axis2.transport.local.LocalTransportSender"/>

It has to be replaced with the following sender/receiver pair.

<transportReceiver name="local" class="org.wso2.carbon.core.transports.local.CarbonLocalTransportReceiver"/>
<transportSender name="local" class="org.wso2.carbon.core.transports.local.CarbonLocalTransportSender"/>
For more information about transports, refer to Transports.
  • No labels