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

Bug 345637

Summary:	Make Resource and derived classes serializable
Product:	[RT] RAP	Reporter:	Rüdiger Herrmann <ruediger.herrmann>
Component:	RWT	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	unspecified
Target Milestone:	1.5 M1
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	342407

Description Rüdiger Herrmann

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

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

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.