James Netherton created CAMEL-16253:
---------------------------------------
Summary: Improve the way that the LRA client determines the new
LRA URL
Key: CAMEL-16253
URL: https://issues.apache.org/jira/browse/CAMEL-16253
Project: Camel
Issue Type: Improvement
Reporter: James Netherton
Assignee: James Netherton
Fix For: 3.9.0
Currently the LRA client gets the LRA URL from the HTTP response header
Long-Running-Action. Which is fine when only one such header is returned and is
ordered in such a way where the new LRA is first in the order of headers.
I was testing with the latest Narayana LRA coordinator bits and noticed that
this fails where there are multiple active LRAs.
We should first check for the Location header, as it will contain the URL to
the LRA. If that's not present, try the Long-Running-Action header if there's
only one of them. Failing those, fallback on the response body which should
also contain the LRA URL.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
