Excessive Patterns

Sure, design patterns are good but there are times when they seem excessive. One particular example that I was pointed to recently is the following Java class:
org.springframework.aop.framework.AbstractSingletonProxyFactoryBean

That is quite a large class name to type, but right there, from the name of the class, you can guess that it uses the singleton, proxy, and abstract factory (assume an abstract factory) design patterns. So, how did they come up with something like that? Programming contest on who could write the most design patterns in a single class?

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s