Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345699 - Make widgets serializable
Summary: Make widgets serializable
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 1.5 M1   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 342407
  Show dependency tree
 
Reported: 2011-05-13 04:45 EDT by Rüdiger Herrmann CLA
Modified: 2011-07-10 09:41 EDT (History)
0 users

See Also:

Attachments
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-05-13 04:45:17 EDT 
For RWT sessions to be able to be clustered, all widgets (class Widget and derived) must be serializable.
Comment 1 Rüdiger Herrmann CLA 2011-06-03 10:25:58 EDT 
Committed the following changes to CVS HEAD:
* Widget implements SerializableCompatibility
* essential fields inWidget and Control were marked as transient
* all classes derived from Widget have default serialVersionUID. This doesn't mean they are propertly serializable yet. The changes were primarily made keep the number of compiler warnings low.
* as org.eclipse.rap.jface was affected from Widget now implementing serializable, the compiler settings were changed (partial solution for bug 347908)
Comment 2 Rüdiger Herrmann CLA 2011-06-03 12:22:44 EDT 
Made IdGenerator, ItemHolder and MenuHolder serializable in order to finally make make Resource and derived classes serializable (bug 345637)
Comment 3 Rüdiger Herrmann CLA 2011-07-10 09:41:32 EDT 
Remaining widgets are now serializable. Changes are in CVS HEAD.