Bug 333560 - Generating Externalizable writeObject and readObject for Java class like equals() or hashcode()
Summary: Generating Externalizable writeObject and readObject for Java class like equa...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-05 06:42 EST by Archanaa CLA
Modified: 2011-01-05 08:19 EST (History)
3 users (show)

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 Archanaa CLA 2011-01-05 06:42:35 EST 
Build Identifier: 20100218-1602

It is a well known fact that Object serialization is quite heavy.  The recommended performance tip often is for the developer to implement Externalizable instead of Serializable for certain classes and implement the writeExternal and readExternal. This is a feature request to provide source code generation of writeExternal and readExternal by providing a dialog box where the user can select which attributes are to be written and read as well as the order in which they have to be written and read. Then eclipse would generate the writeString(..)/writeInt(..)/writeObject(..) code automatically. This would help programmers save time in implementing the externalizable interface and they would be encouraged to do so for multiple classes easily if required. 

Reproducible: Always
Comment 1 Olivier Thomann CLA 2011-01-05 08:16:04 EST 
Move to JDT/UI