Over a million developers have joined DZone.

1942 Classes: Statistics About Spring 2.5

· Java Zone

Discover how AppDynamics steps in to upgrade your performance game and prevent your enterprise from these top 10 Java performance problems, brought to you in partnership with AppDynamics.

Frameworks are growing with every release. Classes are changed, removed and added. In this series I zoom in on some well known projects and analyze their class names with completely meaningless statistics. First: Spring 2.5.

To get these statistics, I wrote a script that analyzed all classes. They get chopped up on word boundaries, so for ContextAwareFactoryBean the words Context, Aware, Factory and Bean are counted. From the output I generated a Class Cloud.

Spring is a framework of Factories, Beans, and Exceptions

There are 1942 classes currently in Spring. Of those, 213 classes contain the word Factory. Even more classes contain the word Bean. Spring is clearly a framework that loves factories and beans. There is even a FactoryBean class.

Another high score partial class name is the Exception. Exactly 197 classes have that in their class name. From the humble BindException to the fine-grained JdbcUpdateAffectedIncorrectNumberOfRowsException.

Class Cloud (click to enlarge)

Spring 2.5 statistics Class Cloud

Top 10 of partial class names

  • Bean: 239
  • Factory: 213
  • Exception: 197
  • Abstract: 158
  • Context: 112
  • Source: 97
  • Utils: 89
  • Transaction: 85
  • Resolver: 79
  • Request: 78

Longest class name

The grand prize goes to two classes: AbstractInterruptibleBatchPreparedStatementSetter and AbstractTransactionalDataSourceSpringContextTests

Both have a length of 49 characters!

Stay tuned for more useless statistics for other well known projects! If you have suggestions for which projects you want to see, please let me know in the comments!

From http://stuq.nl

The Java Zone is brought to you in partnership with AppDynamics. AppDynamics helps you gain the fundamentals behind application performance, and implement best practices so you can proactively analyze and act on performance problems as they arise, and more specifically with your Java applications. Start a Free Trial.


{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}