Skip to main content
Jump to: navigation, search

Difference between revisions of "ToString() generation"

(Must have)
(Planned features)
Line 30: Line 30:
* Changing the order of the fields [[Image:Ok_green.gif]]
* Changing the order of the fields [[Image:Ok_green.gif]]
* User documentation (help)
* User documentation (help)
* Unit tests
* Unit tests [[Image:Progress.gif]]
=== Should have ===
=== Should have ===
Line 44: Line 44:
** Spring Framework's ToStringCreator
** Spring Framework's ToStringCreator
** String concatenation [[Image:Ok_green.gif]]
** String concatenation [[Image:Ok_green.gif]]
** StringBuilder/StringBuffer
** StringBuilder/StringBuffer [[Image:Ok_green.gif]]
** String.format()
** String.format()
** Single return value (e.g. if only one field is chosen, for existing primary keys or Objects with 'names')
** Single return value (e.g. if only one field is chosen, for existing primary keys or Objects with 'names')

Revision as of 06:39, 11 July 2008


The toString() method is widely used to represent objects as human-readable text and practically every class should implement it. Usually it is very simple: generated string contains the object type and lists values of the most important fields. That's why process of writing such methods can easilly be automated. Eclipse, as the best java IDE in the world, should include functionality of automatic toString() method generation to make its users lives even simpler. Implementing it is the aim of this project.

There were many bugs posted regarding this problem, see bug 26070 for details.

This project is part of 2008 Google Summer of Code.


  • CVS: (TBD)

Planned features

  • Legend
Glass.gif Needs some investigation
Progress.gif Patch in progress
Ok green.gif Bug fixed / Feature added

Must have

  • Integration with 'Generate hashCode() and equals()' dialog
  • Turning generators on/off separately
  • Changing the output string format with templates Ok green.gif
  • Changing the order of the fields Ok green.gif
  • User documentation (help)
  • Unit tests Progress.gif

Should have

  • Option to use getters instead of accessing the fields directly
    • Using fields as well as methods (including getters), also inherited ones Ok green.gif
  • Option to skip fields with null value Ok green.gif
  • Option to ignore default toString() of arrays and list elements instead (using Arrays.toString()) Ok green.gif
  • Option to set the maximum number of elements to list from arrays/Collections (helping toString(...) methods)Ok green.gif
  • Option to chose the insertion point of the method (as this is already there for equals() and hashCode()) Ok green.gif
  • Support multiple styles (per project option) Progress.gif
    • Apache Commons-Lang ToStringBuilder
    • Spring Framework's ToStringCreator
    • String concatenation Ok green.gif
    • StringBuilder/StringBuffer Ok green.gif
    • String.format()
    • Single return value (e.g. if only one field is chosen, for existing primary keys or Objects with 'names')

Nice to have

  • Ability to add different implementations of the toString generator or use multiple code templates (e.g. extension points)
  • Change hashCode and equals generators to optionally use getters
    • Change hashCode and equals generators to support inherited fields and methods
  • Annotations (would require Java5 though)
  • Refactorings if e.g. a field is renamed/removed/added (consider save actions. mark fields for permanent exclusion by)
  • NLS support (if desirable in toString)


  • Code Template: The template used to generate the method signature and body of the toString() method
  • Output String Format: The format of the String generated by the implementation of the toString() method

Community proposals

Feel free to add your ideas

  • Nice to have: Accessible through quickfix/content assistant
  • Nice to have: Support options for include/exclude hashcode, super.toString(), class name, use System.identityHashCode() or Object's hashCode()
  • Nice to have: Integration with Detail Formatters from the Debugger

Code Template suggestion 1

An example for an easily editable format:

public String toString()
    return super.toString ()
        + " (field=" + field
        + ", field2=" + field2
        + ")"

This allows to reorder lines by moving (and replacing " (" with ", " in one-of-many cases). Faster than using StringBuilder() or any other way. Fields can be added and removed with least amount of fuzz. Code and result is readable for humans. No ambiguity of result (only "null" and null can't be told apart). Also, the format is easily parsable if you want to offer a "do it again" dialog.

Things to keep in mind:

  • The current formatter (where to put blanks and the curly braces)
  • Use the field directly or call the getter. Direct access is faster but breaks when a getter is overloaded in a subclass. 07:23, 15 May 2008 (EDT)

Code Template suggestion 2

public String toString()
    return String.format("%s[field=%s, field2=%s]", super.toString(), field, field2);
  • Reordering of fields is done in the dialog and the toString() method is regenerated
  • No String concatenation required
  • Still easy to add new fields manually if desired
  • Bad to see which fields are associated with which variables, as they are far apart

Getting the source

For source code, check the latest patch submitted to bug 26070.

Back to the top