Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345595 - Make Device and Display serializable
Summary: Make Device and Display 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-12 09:20 EDT by Rüdiger Herrmann CLA
Modified: 2011-05-27 11:53 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-12 09:20:20 EDT 
As Display (derived from Device) is an integral part of a session, it must implement java.io.Serializable and comply with the requirements for serializable objects to allow RWT sessions to be clustered.
Comment 1 Rüdiger Herrmann CLA 2011-05-27 11:53:41 EDT 
Device and Display now implement Serializable interface, made fields transient where necessary. Added test cases for Device and Display that ensure proper internal state after deserialization.
Compiler settings for org.eclipse.rap.ui.workbench were changed to treat cases where a class implements Serializable but does not provide a serialVersionUID field as warnings.
Changes are in CVS HEAD.