Bug 353117 - Investigate running clustered RWT instances on OSGi
Summary: Investigate running clustered RWT instances on OSGi
Status: ASSIGNED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.5   Edit
Hardware: All All
: P3 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 358557 359405 361971 361110 361554
Blocks: 341761
  Show dependency tree
 
Reported: 2011-07-26 10:20 EDT by Rüdiger Herrmann CLA
Modified: 2011-10-26 05:58 EDT (History)
0 users

See Also:

Attachments
Prototype (39.68 KB, patch)
2011-09-29 07:27 EDT, Rüdiger Herrmann CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rüdiger Herrmann CLA 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 CLA 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.