synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dushan Sachinda Abeyruwan (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SYNAPSE-913) Pass Through HTTP Transport for Synapse and Using the Pass Through Transport by Default
Date Fri, 05 Oct 2012 10:42:04 GMT

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

Dushan Sachinda Abeyruwan edited comment on SYNAPSE-913 at 10/5/12 10:40 AM:
-----------------------------------------------------------------------------

 I did test the patch with REST API clone mediator and seems its not working properly,seems
like only the first message always called to the  destination SUCCESSFULLY and others targets
calls the endpoint with empty headers and payload values.. any thoughts on this?


<api name="ABCD-ScatterGather-BestPrice" context="/ABCD">
      <resource methods="POST GET">
         <inSequence>
            <clone>
               <target>
                  <endpoint key="ABCV1"/>
               </target>
               <target>
                  <endpoint key="ABCV2"/>
               </target>
               <target>
                  <endpoint key="ABCV3"/>
               </target>
            </clone>
         </inSequence>
         <outSequence>
            <aggregate>
               <completeCondition>
                  <messageCount min="-1" max="-1"/>
               </completeCondition>
               <onComplete expression="//priceResponse">
                  <enrich>
                     <source clone="true"
                             xpath="//priceResponse[not(preceding-sibling::priceResponse/unitPrice
&lt;= unitPrice) and not(following-sibling::priceResponse/unitPrice &lt; unitPrice)]"/>
                     <target type="body"/>
                  </enrich>
                  <send/>
               </onComplete>
            </aggregate>
         </outSequence>
      </resource>
   </api>



                
      was (Author: dushan@wso2.com):
     I did test the patch with REST API clone mediator and seems its not working properly,seems
like only the first message always called to the  destination SUCCESSFULLY and otherstargets
calls the endpoint with empty headers and payload values.. any thoughts on this?


<api name="ABCD-ScatterGather-BestPrice" context="/ABCD">
      <resource methods="POST GET">
         <inSequence>
            <clone>
               <target>
                  <endpoint key="ABCV1"/>
               </target>
               <target>
                  <endpoint key="ABCV2"/>
               </target>
               <target>
                  <endpoint key="ABCV3"/>
               </target>
            </clone>
         </inSequence>
         <outSequence>
            <aggregate>
               <completeCondition>
                  <messageCount min="-1" max="-1"/>
               </completeCondition>
               <onComplete expression="//priceResponse">
                  <enrich>
                     <source clone="true"
                             xpath="//priceResponse[not(preceding-sibling::priceResponse/unitPrice
&lt;= unitPrice) and not(following-sibling::priceResponse/unitPrice &lt; unitPrice)]"/>
                     <target type="body"/>
                  </enrich>
                  <send/>
               </onComplete>
            </aggregate>
         </outSequence>
      </resource>
   </api>



                  
> 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: patch_with_some_fixes.txt, 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Mime
View raw message