Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 343080

Summary:	Handle invalid ServiceHandler id parameter
Product:	[RT] RAP	Reporter:	Ralf Sternberg <rsternberg>
Component:	RWT	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	1.4
Target Milestone:	1.5 M6
Hardware:	PC
OS:	Linux
Whiteboard:

Description Ralf Sternberg

2011-04-17 17:46:10 EDT

When the server receives a request for a service handler that has not been registered, it silently answers with the initial HTML page. This can make it hard to track down a problem caused by a misspelled service handler id.

I think we should throw an exception when the parameter "custom_service_handler" is present in a request but has an invalid value.

Comment 1 Rüdiger Herrmann

2011-04-18 03:41:23 EDT

+1 for throwing an exception

Comment 2 Ralf Sternberg

2012-03-14 19:23:14 EDT

Now an InvalidArgumentException is thrown in ServiceManager in case of an invalid service handler id, leading to an HTTP 500. This is an inappropriate response code (see also bug 371935), but at least the error gets noticed. I opened bug 374327 for registering service handlers by path as well.

Changes are in CVS HEAD.