[WW-4050] AnnotationValidationInterceptor should consult UnknownHandler before throwing NoSuchMethodException

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3.14
• Fix Version/s: 2.5.10
• Assignee: Lukasz Lenart
• Reporter: Azuo Lee
• Created: 18/Apr/13 07:03
• Updated: 13/Feb/17 09:50
• Resolved: 02/Jan/17 08:01

Description

If a NoSuchMethodException is caught when invoking getActionMethod(), AnnotationValidationInterceptor should first give any configured UnknownHandler a shot, before throwing the exception directly, just as what DefaultActionInvocation.invokeAction() does.

Any unknown Action or unknown Result is currently handled by Dispatcher.serviceAction(), and a 404 error code will be returned as expected. But an unknown Method will raise a 500 error, the only way to avoid this is to configure an UnknownHandler. Therefore, AnnotationValidationInterceptor won't inspect UnknownHandler at all...

GET /foo/list  404 (Action "foo" not found)
GET /bar/list  200
GET /bar/print 500 (Method "print" not found, 404 is expected instead of 500)

Issue Links

• relates to: WW-4693 How to handle 404 when using wildcard instead of error 500 when the wildcard method doesn't exist