Page Comparison

...

The following diagram depicts a scenario where a REST client communicates with a REST service using WSO2 EI. Apache Tcpmon is used solely for monitoring the communication between WSO2 EI and the back-end service and has no impact on the messages passed between the ESB WSO2 EI and back-end service. For this particular scenario, the cURL client is used as the REST client, and the basic JAX-RS sample is used as the back-end REST service.

...

Configure and deploy the JAX-RS Basics sample by following the instructions for building and running the sample on the JAX-RS Basics page.

Start

the ESB and

WSO2 EI and change the configuration as follows:

Code Block

language	html/xml

<definitions xmlns="http://ws.apache.org/ns/synapse">
   <sequence name="fault">
      <log level="full">
         <property name="MESSAGE" value="Executing default sequence"/>
         <property name="ERROR_CODE" expression="get-property('ERROR_CODE')"/>
         <property name="ERROR_MESSAGE" expression="get-property('ERROR_MESSAGE')"/>
      </log>
      <drop/>
   </sequence>
   <sequence name="main">
      <log/>
      <drop/>
   </sequence>
   <api name="testAPI" context="/customerservice">
      <resource methods="POST" url-mapping="/customers">
         <inSequence>
            <send>
               <endpoint>
                  <address uri="http://localhost:8280/jaxrs_basic/services/customers/customerservice"/>
               </endpoint>
            </send>
         </inSequence>
         <outSequence>
            <send/>
         </outSequence>
      </resource>
   </api>
</definitions>

In this proxy configuration, testAPI intercepts messages that are sent to the relative URL /customerservice/customers and sends them to the relevant endpoint by appending the url-mapping of the resource tag to the end of the endpoint URL.

Start tcpmon and make it listen to port 8280 of your local machine. It is also important to set the target host name and the port as required.
We will now test the connection by sending a POST message that includes a payload inside an HTML body.
Go to the terminal and issue the following command:
curl -v -H "Content-Type: application/xml" -d "<Customer><id>123</id><name>John</name></Customer>" http://localhost:8280/customerservice/customers
The following reply message appears in the console:
Code Block
language html/xml
<Customer> <id>132</id> <name>John</name> </Customer>
Now send the same POST message but without the enclosed data:
curl -v -H "Content-Type: application/xml" -d "" http://localhost:8280/customerservice/customer

The tcpmon output shows the same REST request that was sent by the client, demonstrating that the ESB WSO2 EI handled the POST message regardless of whether it included a payload. However, you would need to configure the back-end service to handle such requests, or the application server will throw exceptions.

...

Sending a POST message with query parameters is an unusual scenario, but the ESB supports it with no additional configuration. The ESB WSO2 EI forwards the message like any other POST message and includes the query parameters.

...

Versions Compared

Old Version 2

New Version 3

Key