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

Bug 353117

Summary:

Investigate running clustered RWT instances on OSGi

Product:

[RT] RAP

Reporter:

Rüdiger Herrmann <ruediger.herrmann>

Component:

RWT

Assignee:

Project Inbox <rap-inbox>

Status:

ASSIGNED ---

QA Contact:

Severity:

enhancement

Priority:

Version:

1.5

Target Milestone:

---

Hardware:

All

OS:

All

Whiteboard:

Bug Depends on:

358557, 359405, 361971, 361110, 361554

Bug Blocks:

341761

Attachments:

Description	Flags
Prototype	none

Description Rüdiger Herrmann

2011-07-26 10:20:33 EDT

Can RWT on OSGi be clustered? 
The most apparent challenge seems to be class loading issues (what else?) when deserializing session state.

Comment 1 Rüdiger Herrmann

2011-09-29 07:27:15 EDT

Created attachment 204281 [details]
Prototype

With this patch, the testButtonEntryPoint test from the JettySessionFailover_Test run successfully.
The changes are meant to outline an approach to control the class-loading during deserialization. It uses the fact that Jetty consults the context-loader of the current thread while deserializing a session.
Upon serialization of the SessionStore, information about classes and their respective (bundle-)class-loaders is serialized along with the session data. The SessionStore is deserialized before any other object. This circumstance allows to read the class-loader-information and equip the context-loader with it so that supsequent attempts to load classes succeed.