[ 
https://issues.apache.org/jira/browse/SYNAPSE-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468488#comment-13468488
 ] 

Amila Chinthaka Suriarachchi commented on SYNAPSE-913:
------------------------------------------------------

I think this problem is with the message synapse send to back end. 

POST /service/EchoService HTTP/1.1

SOAPAction: "urn:buyStocks.2"

routing: xadmin;server1;community#1.0##

Content-Type: text/xml; charset=UTF-8

Content-Length: 1024

Host: 127.0.0.1:9005

Connection: Keep-Alive



<?xml version='1.0' encoding='UTF-8'?>
   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
      <soapenv:Header>
         <routing 
xmlns="http://someuri";>xadmin;server1;community#1.0##</routing>
      </soapenv:Header>
      <soapenv:Body>
         <m:skcotSyub xmlns:m="http://services.samples/xsd"; 
xmlns:m0="http://services.samples/xsd";>
            <redro>
               <lobmys>IBM</lobmys>
               <DIreyub>asankha</DIreyub>
               <ecirp>140.34</ecirp>
               <emulov>2000</emulov>
            </redro>
            <redro>
               <lobmys>MSFT</lobmys>
               <DIreyub>ruwan</DIreyub>
               <ecirp>23.56</ecirp>
               <emulov>8030</emulov>
            </redro>
            <redro>
               <lobmys>SUN</lobmys>
               <DIreyub>indika</DIreyub>
               <ecirp>14.56</ecirp>
               <emulov>500</emulov>
            </redro>
            <redro>
               <lobmys>GOOG</lobmys>
               <DIreyub>chathura</DIreyub>
               <ecirp>60.24</ecirp>
               <emulov>40000</emulov>
            </redro>
            <redro>
               <lobmys>IBM</lobmys>
               <DIreyub>asankha</DIreyub>
               <ecirp>140.34</ecirp>
               <emulov>2000</emulov>
            </redro>
            <redro>
               <lobmys>MSFT</lobmys>
               <DIreyub>ruwan</DIreyub>
               <ecirp>23.56</ecirp>
               <emulov>803000</emulov>
            </redro>
            <redro>
               <lobmys>SUN</lobmys>
               <DIreyub>indika</DIreyub>
               <ecirp>14.56</ecirp>
               <emulov>500

For some reason it does not send the complete message to back end.
                
> 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]

Reply via email to