This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.
Writing a Synapse Handler
This section gives an introduction to what a handler is and describes how you can write a synapse handler by walking you through a basic example.
Introduction to handlers
Handlers can be used to process requests in a scenario where you have multiple requests, and each request needs be processed in a specific manner. A Handler defines the interface that is required to handle the request and concreteHandlers are to handle requests in a specific manner based on what needs to be done with regard to each type of request. The diagram below illustrates this.
Synapse handler is the interface used to register server response callbacks. Synapse handler provides the abstract handler implementation that executes the request in flow, request out flow, response in flow and response out flow.
The diagram below is an illustration of how the specified flows execute in the abstract handler implementation.
Request in flow
public boolean handleRequestInFlow(MessageContext synCtx);
This executes when the request reaches the synapse engine.
Request out flow
public boolean handleRequestOutFlow(MessageContext synCtx);
This executes when the request goes out of the synapse engine.
Response in flow
public boolean handleResponseInFlow(MessageContext synCtx);
This executes when the response reaches the synapse engine.
Response out flow
public boolean handleResponseOutFlow(MessageContext synCtx);
This executes when the response goes out of the synapse engine.
The diagram below illustrates the basic component structure of the WSO2 EI and how the flows mentioned above execute in the request path and response path.
Now that you understand what a handler is, let's see how you can write a concrete Synapse handler.
Writing a concrete Synapse handler
The easiest way to write a concrete Synapse handler is to extend the org.apache.synapse.AbstractSynapseHandler
class. You can also write a concrete Synapse handler by implementing org.apache.synapse.SynapseHandler
, which is the SynapseHandler interface.
Following is an example Synapse handler implementation that extends the org.apache.synapse.AbstractSynapseHandler
class:
public class TestHandler extends AbstractSynapseHandler { private static final Log log = LogFactory.getLog(TestHandler.class); @Override public boolean handleRequestInFlow(MessageContext synCtx) { log.info("Request In Flow"); return true; } @Override public boolean handleRequestOutFlow(MessageContext synCtx) { log.info("Request Out Flow"); return true; } @Override public boolean handleResponseInFlow(MessageContext synCtx) { log.info("Response In Flow"); return true; } @Override public boolean handleResponseOutFlow(MessageContext synCtx) { log.info("Response Out Flow"); return true; } }
Deploying the Synapse handler
When you write you own Synapse handler you can deploy it either as an OSGi bundle or a JAR file to WSO2 EI.
Engaging the Synapse handler
To engage the deployed Synapse handler, you need to add the following configuration to the <EI_HOME>/conf/synapse-handlers.xml
file.
<handlers> <handler name="TestHandler" class="package.TestHandler"/> </handlers>