Re: RestHttpOperationInvoker and SimpleHttpOperationInvoker

Jinmei- I think I am mistaken about the use of Apache's HTTP Components. I know at one time I experimented with using Apache's HTTP Components as more robust solution (than JDK's URLConnection/HttpURLConnection) that is supported by *Spring's* RestTemplate for client HTTP access, but I see

Re: RestHttpOperationInvoker and SimpleHttpOperationInvoker

Response below... On Fri, May 26, 2017 at 11:49 AM, Jinmei Liao wrote: > John, thank you for the detailed response. So the difference between these > two are the way request url is obtained, the RestHttpOperationInvoker > obtained the url from the returned LinkIndex map, while this > SimpleHttpO

Re: RestHttpOperationInvoker and SimpleHttpOperationInvoker

I should also add that the RestHttpOperationInvoker even makes use [1] of the SimpleHttpOperationInvoker as a fallback. There is also configu

Re: RestHttpOperationInvoker and SimpleHttpOperationInvoker

John, thank you for the detailed response. So the difference between these two are the way request url is obtained, the RestHttpOperationInvoker obtained the url from the returned LinkIndex map, while this SimpleHttpOperationInvoker construct the url itself and eventually gets something like ".../

Re: RestHttpOperationInvoker and SimpleHttpOperationInvoker

Hi Jinmei- *> Do we know why in our admin rest api, we have these two kind of OpeationInvokers* Yes. The Javadoc [1] somewhat explains

RestHttpOperationInvoker and SimpleHttpOperationInvoker

Hi, team, Do we know why in our admin rest api, we have these two kind of OpeationInvokers, it looks like when RestHttpOperationInvoker failed to find the resource, it will use the SimpleHttpOperationInvoker to try again, but shouldn't that also fail as well? Here is some of the logic I found in