[ 
https://issues.apache.org/jira/browse/SYNAPSE-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hiranya Jayathilaka updated SYNAPSE-937:
----------------------------------------

    Fix Version/s: 3.0
    
> [PTT] Message not get built in response path when transport switching
> ---------------------------------------------------------------------
>
>                 Key: SYNAPSE-937
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-937
>             Project: Synapse
>          Issue Type: Bug
>          Components: Transports
>            Reporter: Isuru Udana Loku Narangoda
>            Assignee: Hiranya Jayathilaka
>            Priority: Critical
>             Fix For: 3.0
>
>         Attachments: patch_for_both_reqest_response_path.patch, 
> SYNAPSE-937.patch
>
>
> When using Passthough transport, When transport switching is happening in 
> response path, message has to be built.
> For an example in the following sample configuration and an empty envelope 
> get written to a file as message is not built when switching transports from 
> http to vfs.
> <proxy name="StockQuoteProxy" xmlns="http://ws.apache.org/ns/synapse";>
>         <target>
>             <endpoint>
>                 <address 
> uri="http://localhost:9000/services/SimpleStockQuoteService"/>
>             </endpoint>
>             <outSequence>
>                 <property action="set" name="OUT_ONLY" value="true"/>
>                 <send>
>                     <endpoint>
>                         <address uri="vfs:file:///home/isuru/response"/>
>                     </endpoint>
>                 </send>
>             </outSequence>
>         </target>
> </proxy>

--
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