Why has the accessor methods from the JavaBean specification become the standard for Java development?
- by Dakotah North
The JavaBeans Specification describes a JavaBean as
A Java Bean is a reusable software component that can be manipulated visually
in a builder tool
Since the majority of the lines of code that are written seem to have nothing to do with being manipulated visually in a builder tool, why has the JavaBean specification been the "way" to write object oriented code?
I would like to forgo the traditional getter/setter in favor of Fluent Interfaces all throughout the code, not just in builders but fear doing so since this is traditionally not the way way object oriented code is written in Java.
