Evan, > I can do an ugly hack to look for a cause, and if it matches connection > timeout, pull it from the immediate cause; otherwise, grab the root cause > to handle others (there are other custom exceptions that are wrapped by > RestClientException, hence the reason). > I think just using getCause() should be enough always.
> Was there a reason why the Component's implementation has connection > exception wrapping socket exception? > as Oleg aleady explained "to help distinguish connect timeout from socket (read operation) timeout" In the first case the remote service is probably not running, and in the second it's running but processing takes longer than client wants.
