Everything that's wrong with Java in a single class

Re:Everything that's wrong with Java in a single class by rickmode on Thursday September 20, 2012 @05:22PM (#4550776)

The class combines no less than 6 concepts / design patterns:

  - Abstract
  - Singleton
  - Proxy
  - Factory
  - Bean
  - Interceptors

It's not just a long name. The class makes sense in the context of this framework. The core problem (as others here point out) is that the Java flavor of OOP makes writing this sort of code idiomatic.

On the upside, you feel really smart once you grok all these concepts simultaneously. After a couple years this you get to brand yourself a "Java Architect".

[ Parent | on HN ]

Re:Everything that's wrong with Java in a single class by moondowner on Friday September 21, 2012 @05:09AM (#4552927)

Agreed, this class is an exception of excellent engineering. Maybe people who don't develop in Spring find it 'wrong', but it's not.

[ Parent | on HN ]

Re:Everything that's wrong with Java in a single class by hcarvalhoalves on Thursday September 20, 2012 @05:30PM (#4550833)

Overengineering at it's best.

[ Parent | on HN ]

Re:Everything that's wrong with Java in a single class by chris_wot on Friday September 21, 2012 @08:11AM (#4553395)

Until, of course, you find you need to use it. Of course, you'll probably never need to use it, nor will you ever see it being used in your particular situation. But hey, it's all over-engineered nonsense, right?

[ Parent | on HN ]

Re:Everything that's wrong with Java in a single class by amalag on Friday September 21, 2012 @10:22AM (#4553844)

This is a great comment. This is what a Java "Engineer" or "Architect" is supposed to understand. It is complex, but seems too abstracted from programming reality that it makes programming simple things more complicated then they have to be.

[ Parent | on HN ]

Re:Everything that's wrong with Java in a single class by chris_wot on Friday September 21, 2012 @11:08AM (#4554056)

All of these things are useful and valid techniques for building scalable, maintainable and extensible code.

Abstract is a pretty basic OO concept. You make an abstract class when you want it to be derived and never used directly.

Singleton is where a class can only ever create one object. Harder than it sounds.

Proxy is where the class interfaces with something else. Again, very useful. Proxies are used by Spring to implement AOP.

Factory - abstracts away the creation of objects, in other words the client object does not need to know how to create objects. It's used extensively in the Spring IoC container.

Beans are object that use simple but powerful conventions of creating reusable components in Java.

Interceptors at used by AOP.

If you use these concepts as they are intended to be used then your code will be cleaner, maintainable and a joy to work with.

[ Parent | on HN ]