Bug 32164 - Serialization methods with private or arbitrary access modifiers should be ignored by "unused private members" compiler check.
Summary: Serialization methods with private or arbitrary access modifiers should be ig...
Status: RESOLVED DUPLICATE of bug 31495
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.1 RC1   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-18 15:50 EST by John P. A. Verhaeg CLA
Modified: 2003-02-19 06:26 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John P. A. Verhaeg CLA 2003-02-18 15:50:41 EST
The following serialization methods defined by the Serializable class have or 
may have private or arbitrary access modifiers even though they may not be 
explicitly referenced by any code.  They should therefore be ignored by "unused 
private members" compiler check:

  private void writeObject(ObjectOutputStream out)
  throws IOException
 
  private void readObject(ObjectInputStream in)
  throws IOException, ClassNotFoundException;
  
  ANY-ACCESS-MODIFIER Object writeReplace()
  throws ObjectStreamException;
  
  ANY-ACCESS-MODIFIER Object readResolve()
  throws ObjectStreamException;
Comment 1 Olivier Thomann CLA 2003-02-18 16:30:06 EST
What build are you using?
Comment 2 John P. A. Verhaeg CLA 2003-02-18 16:31:26 EST
M5.  You guys ought to include this in the version drop-down.
Comment 3 Philipe Mulet CLA 2003-02-18 18:36:08 EST
These 4 methods are no longer reported in build 20030218, along with main(String
[]) and field 'serialVersionUID'.
Comment 4 Philipe Mulet CLA 2003-02-19 06:26:11 EST

*** This bug has been marked as a duplicate of 31495 ***