Programming Groovy 2

2.2 JavaBeans

It was exciting when the concept of JavaBeans was introduced—Java objects would be considered JavaBeans if they followed certain conventions to expose their ​properties​. That raised a lot of hope, but we soon found that to access these properties, calls to mere getters and setters were required. The excitement came crashing down, and developers moved on to create thousands of silly methods in their applications.[15] If JavaBeans were human, they’d be on Prozac. To be fair, the intent of ​JavaBean​ is noble—it made component-based development, application assembly, and integration practical and paved the way for exceptional integrated development environment (IDE) and plug-in development.

Groovy treats JavaBeans with the respect ...