Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345637 - Make Resource and derived classes serializable
Summary: Make Resource and derived classes 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 14:00 EDT by Rüdiger Herrmann CLA
Modified: 2011-06-07 05:27 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 14:00:40 EDT 
Instances of Resource and its derived classes (e.g. FontData, Image, ...) may have either application or session scope, depending on how they have been constructed.
Hence, they 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-06-07 03:26:22 EDT 
Unshared/session-scoped images are now serializable and can be migrated between sessions.
Comment 2 Rüdiger Herrmann CLA 2011-06-07 05:27:01 EDT 
Cursor, Font and Color are serializable now.
As of now, GC is not serializable. It should only be used within a request (i.e. inside a paint listener) and not survive the end of a request.