[
https://issues.apache.org/jira/browse/SYNAPSE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864020#action_12864020
]
Andreas Veithen commented on SYNAPSE-601:
-----------------------------------------
Note that out-in should already be supported in the asynchronous case (i.e.
with WS-Addressing). What the VFS transport doesn't support is synchronous
responses. I'm not sure if there is a meaningful way to implement that. The JMS
transport (and also the mail transport I think) indeed support synchronous
responses, but the scenario is different because both transport protocols have
a built-in correlation mechanism (correlation IDs for JMS and In-Reply-To
headers for mail).
Also note that Stefan is not complaining about the fact that the VFS transport
doesn't support out-in, but about the fact that he has to set OUT_ONLY to true
and then later to false. If I understand correctly, in his scenario he sends
the message to a VFS destination (which is indeed out-only) and then to some
other destination that is out-in. If I remember correctly, we modified the
<send> mediator so that properties can be set inside the mediator (which would
then only apply to the outgoing message, but not to the rest of the flow). This
is probably the best solution here.
With respect to the Stefan's comment that "the behaviour described above is not
compatible with sequences developed with synapse 1.2": that is true, but using
the VFS transport without setting OUT_ONLY will result in a memory leak,
because Synapse will create a callback that is only discarded after 24h (I
think). In this case, I think it is better to trigger an exception than to
preserve strict compatibility.
> VFS transport expects out only pattern in incorrect way
> -------------------------------------------------------
>
> Key: SYNAPSE-601
> URL: https://issues.apache.org/jira/browse/SYNAPSE-601
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.0
> Reporter: Stefan von Brauk
>
> the VFS transports expects that out only message exchange pattern is set and
> throws an exception.
> Thix is incorrect if a VFS endpoint is used in a complex workflow. In this
> case the use r is force to use a workarround like
> <property name="OUT_ONLY" value="true" />
> <send>
> <endpoint key="theVFSendpoint" />
> </send>
> <property name="OUT_ONLY" value="false" />
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
