Revert "Not using httpStatus() method for custom status codes"
This reverts commit b59277f0
Revert "Came back to previous impl for WebClient instrumentation; fixes gh-1442"
This reverts commit bee61a9988.
TraceableExecutorService swallows Exception because `execute` submits a Runnable and ignores the Future's result. It should call the delegates `execute` method instead of the `submit`.
with the current setup we're using the MDC's default interpolation as a default for spring var resolution (which makes no sense)
with this change we're removing the dashes
fixes gh-1396
curently whenever we try to retrieve the http status we get an exception for custom codes
we've migrated to using the raw status code. Also, due to https://github.com/spring-projects/spring-framework/issues/23366 we had to manually wrap the ClientResponse so as we don't throw an exception on httpStatus() method
fixes gh-1393
at the point of creating the configuration class, that bean can use httptracing that can be in progress of being created.
with this fix we're making the call lazy
fixes gh-1354
currently when an exception is thrown upon trying to fetch a Feign client bean, we're trying to fetch the httptracing bean to create a default client. The thing is that httptracing might be in creation
this fix removes the fetching of the httptracing bean since we can use the lazy client
fixes gh-1334
When proxying the various Executor interfaces in ExecutorbeanPostProcessor, the decision of whether or not to use a cglib proxy
was determined by checking if the bean's class is final, but final methods would also cause issues when using cglib. A common
example of such an implementation is DelegatingSecurityContextScheduledExecutorService, which has final methods.
To resolve the issue with ThreadPoolTaskExecutor, AsyncTaskExecutor, and ExecutorService, fall back to the JDK proxy if the
bean has any final methods.
fixes#1336
