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

Bug 371993

Summary:	Cluster tests fail after switching to entrypoints by path
Product:	[RT] RAP	Reporter:	Ralf Sternberg <rsternberg>
Component:	RWT	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	1.5
Target Milestone:	1.5 M6
Hardware:	PC
OS:	Linux
Whiteboard:

Description Ralf Sternberg

2012-02-19 09:55:26 EST

Since entrypoints must now be registered by path instead of name, I tried to adapt the cluster tests to this change. What I did was:
* registered the entrypoint by path "/rap" instead of name "default" in RWTStartup
* removed the "startup=default" parameter in RWTClient

After this, all tests in rap.rwt.cluster.test failed with a java.io.NotSerializableException that I was not able to narrow down.
As a temporary workaround, I changed the registration in RWTStartup back to register-by-name using an internal compatibility API, but even this didn't change anything.

Comment 1 Ralf Sternberg

2012-02-19 10:24:37 EST

Temporarily disabled cluster tests in runtime/pom.xml

Comment 2 Ralf Sternberg

2012-03-15 18:23:29 EDT

- The cluster test fixture needed to be adapted to the recent entrypoint-by-path changes (bug 365633), GET/POST changes (bug 372296), and protocol changes (bug 371252).
- Removed entrypoint caching from EntryPointUtil. Entrypoint registrations must not end up in session store, and the caching was not needed anymore because the results are deterministic, and are not requested very often.
- Re-enabled cluster tests.