[
https://issues.apache.org/jira/browse/SYNAPSE-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749804#comment-13749804
]
Isuru Udana Loku Narangoda commented on SYNAPSE-944:
----------------------------------------------------
Yes. This is obsolete now and already addressed in new BlockingClient.
I will close the issue.
> MessageProcessor retry for SOAP faults
> --------------------------------------
>
> Key: SYNAPSE-944
> URL: https://issues.apache.org/jira/browse/SYNAPSE-944
> Project: Synapse
> Issue Type: Bug
> Reporter: Isuru Udana Loku Narangoda
> Assignee: Charith Dhanushka Wickramarachchi
> Attachments: SYNAPSE-944.patch
>
>
> Currently when a SOAP Fault is thrown from backend server, Message Processor
> tries to send the message again.
> In most of the cases as SOAP faults are thrown for business level (data)
> issues, it should not retry and should give the control to the user to handle
> it.
> SOAP fault should be treated as a normal SOAP message. This is the behavior
> of Proxy service (SOAP faults are dispatched to the OutSequence).
> So ideally SOAP Faults should arrive to the replySequence of MessageProcessor.
--
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]
