Project

General

Profile

Bug #690

Missing some error logging when wadl file not found

Added by Mike Stults almost 9 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
04/30/2015
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

Update error handling, error reporting, and status code report to browser when wadl file is specified in configuration, but not found or not readable.

History

#1 Updated by Mike Stults over 8 years ago

revision 12229 - add new endpoint for v2/swagger, issue 688, and update error handling for wadl endpoint, issue 690

should get an error message returned now when swagger file is missing, should have same error output as v2/swagger.

#2 Updated by Mike Stults over 8 years ago

  • Status changed from New to Resolved

#3 Updated by Robert Weekly over 8 years ago

  • Resolution set to Fixed
  • Status changed from Resolved to Closed

Confirmed to work. Error for not finding a service WADL (or finding an invalid one) is logged to $SERVICE.log and localhost_access_$DATE.txt files in the tomcat logs.

Also available in: Atom PDF