Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345865 - Consider making Accessible serializable
Summary: Consider making Accessible 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-15 21:44 EDT by Rüdiger Herrmann CLA
Modified: 2011-07-11 05:40 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-15 21:44:57 EDT 
Accessible objects are part of Control and can be reached via Control#getAccessible(). Therefore they could/should be serialize dwhen Controls are serialized. On the other hand, the current Accessible implementation doesn't do anything real. Thus it might speed up the serialization process if the reference to the accessible object in Control would be transient and recreated after deserialization.
Comment 1 Rüdiger Herrmann CLA 2011-07-11 05:40:51 EDT 
As the Accessible implementation doesn't do anything real, I decided to not serialize the Accessible objects for now.
Changes are in CVS HEAD