How To Achieve “one-way” Exchange Pattern With The new HTTP Connector In Mule?

0
votes

I am quoting from Mule official documentation

On the old HTTP Connector, both for inbound and outbound endpoints, it was possible to set up the exchange-pattern so that messages only went in one direction, so inbound endpoints would send no request back to the requestor, and outbound endpoints would not listen for a response to their requests. The new HTTP Connector always has a two way communication.

It seems that one-way is not an option in The new HTTP Connector, but i do need a one-way exchange pattern in my application (the whole architecture of my app and subsidiaries that mostly are services on different servers around the country) to perform code like below :

<until-successful objectStore-ref="objectStore" maxRetries="${MaximumRetry}" secondsBetweenRetries="${RetryInterval}">
    <http:outbound-endpoint address="${EMCURL}" exchange-pattern="one-way">
        <transformer ref="contentTypeTextXML"/>
    </http:outbound-endpoint>
</until-successful>

So what are my options in migrating to new HTTP Connectors? I see three options

  1. Find another way (maybe i shouldn't use HTTP connectors after all).
  2. Find a Hacker Solution
  3. Use the old http:outbound-endpoints, and stick to Mule 3.6

Which one do you suggest?

thank you

1
javamuleesb

1 Answers

2
votes

If you aren't interested in the response simply place the HTTP request in a async scope or in another flow that is called through a one way vm endpoint.