It would be beneficial to designers integrating with REST services to natively provide instructive messages for connectivity exceptions. OpenApi/Swagger describes http response codes but not java exceptions outside normal http flow. For example this exception is captured for connection errors:
com.dstawd.processengine.model.flowobjects.AutomatedActivityFlowObject.executeService(ProcessInstance, String, String, Element):
Service failed to execute. Error: java.lang.IllegalAccessException: The response object is javax.ws.rs.ProcessingException, not an fastrequirementsapi.ApiException
Service Error Stack:
It would be beneficial for these types of errors to expose the actual java exception or a friendlier message to the designer. This information can be found in log files that typical designers do not have access to.
