[
https://issues.apache.org/jira/browse/SYNAPSE-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468511#comment-13468511
]
Pradeep Fernando commented on SYNAPSE-913:
------------------------------------------
Hi,
message formats after applying the patch
request:
POST /EchoService/EchoServlet HTTP/1.1
valid: true
SOAPAction: placeOrders
Content-Type: text/xml
Content-Length: 512
Host: 127.0.0.1:9090
Connection: Keep-Alive
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Body>
<m0:placeOrders xmlns:m0="http://services.samples";>
<m0:order><m0:price>151.28</m0:price><m0:quantity>15</m0:quantity><m0:symbol>ABC</m0:symbol></m0:order>
<m0:order><m0:price>200.28</m0:price><m0:quantity>160</m0:quantity><m0:symbol>PQR</m0:symbol></m0:order>
<m0:order><m0:price>140.28</m0:price><m0:quantity>120</m0:quantity><m0:symbol>XYZ</m0:symbol></m0:order>
</m0:placeOrders>
response:
HTTP/1.1 200 OK
Date: Wed, 03 Oct 2012 11:43:34 GMT
Server: Jetty/4.2.27 (Linux/3.2.0-23-generic amd64 java/1.6.0_34)
Content-Type: text/xml
Transfer-Encoding: chunked
200
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Body>
<m0:placeOrders xmlns:m0="http://services.samples";>
<m0:order><m0:price>151.28</m0:price><m0:quantity>15</m0:quantity><m0:symbol>ABC</m0:symbol></m0:order>
<m0:order><m0:price>200.28</m0:price><m0:quantity>160</m0:quantity><m0:symbol>PQR</m0:symbol></m0:order>
<m0:order><m0:price>140.28</m0:price><m0:quantity>120</m0:quantity><m0:symbol>XYZ</m0:symbol></m0:order>
</m0:placeOrders>
0
working request/respons (without applying the patch)
request:
POST /EchoService/EchoServlet HTTP/1.1
Content-Type: text/xml; charset=UTF-8
valid: true
SOAPAction: "placeOrders"
Transfer-Encoding: chunked
Host: 127.0.0.1:9090
Connection: Keep-Alive
User-Agent: Synapse-HttpComponents-NIO
223
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Body>
<m0:placeOrders xmlns:m0="http://services.samples";>
<m0:order><m0:price>151.28</m0:price><m0:quantity>15</m0:quantity><m0:symbol>ABC</m0:symbol></m0:order>
<m0:order><m0:price>200.28</m0:price><m0:quantity>160</m0:quantity><m0:symbol>PQR</m0:symbol></m0:order>
<m0:order><m0:price>140.28</m0:price><m0:quantity>120</m0:quantity><m0:symbol>XYZ</m0:symbol></m0:order>
</m0:placeOrders>
</soapenv:Body></soapenv:Envelope>
0
> Pass Through HTTP Transport for Synapse and Using the Pass Through Transport
> by Default
> ---------------------------------------------------------------------------------------
>
> Key: SYNAPSE-913
> URL: https://issues.apache.org/jira/browse/SYNAPSE-913
> Project: Synapse
> Issue Type: Improvement
> Components: Core, Transports
> Environment: Any
> Reporter: Hiranya Jayathilaka
> Fix For: FUTURE
>
> Attachments: SYNAPSE_PASS_THRU_8.patch
>
>
> This improvement has 2 main aspects:
> 1. Contributing the pass through HTTP transport developed at WSO2 to Synapse
> 2. Modifying Synapse to use the pass through HTTP transport as the default
> (this requires some minor changes to the transport too)
> The pass through transport, as it stands now, can only be used for simple
> pass through, static routing and header based routing scenarios. It cannot be
> used for any scenario where content lookup or manipulation is required. This
> effort makes the pass through transport one of the core transports of
> Synapse, and modifies Synapse and the transport in a way so that the
> transport can be used in any scenario without restrictions.
> See the conversations at:
> http://old.nabble.com/Message-Relay-Support-for-Synapse-to33693068.html
> http://mail-archives.apache.org/mod_mbox/synapse-dev/201209.mbox/browser
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
