For people who favour XML configs & complexity – Go figure out other world of programming.

No RAD with spring, too complex for simple applications & too becomes too complicated for big applications. The result – spend more money maintaining it & get worse.

A framework should make life easy & faster development time. If you have complex items, you can use plugins to overcome.

Look at springframework.org, you guys will love it. I use Spring + Hibernate for medium sized apps – its fairly straight forward & very easy to work with. We develop modules like piece o cake.

More easy to me.

All of you spring fans, have fun with spring! (Seriously! If it’s your way, it is…)

All of you java programmers, who don’t like spring/hibernate: they are not for speeding things up. While people is investing in learning frameworks (actually learning to deal with framework-specific Exceptions), I’ve already written the thing required for the customer. With plain old java objects. And it was fun! Done it my way with my existing self-explanatory java code library. I think it’s more fun to write java, than study the latest framework trend.

All the best,

Johnny

Performance :!
Maintenance :!
Re-usability :!
Domain Driven Design :!

Your like the kid who still thinks everyone else should clean up their mess in the kitchen.

in this way instead of having to list 1000 DAO + 200 Service beans + 300 bizz objects all in xml ( what a hell it will be), only Tx mgr + myDataSource + superDao is required to list in the xml…. all my 1000 DAOs are subclassed from this superDao.

thanks to great CGLib / AOP…….

I wish the day Sun can make the java.lang.Object having the similar method of CGLib enhancer….

“J2EE should be easier to use” why? distributed processing and large scaled systems are not easy to develop, are they? Unless you want use JEE’s advanced features to develop even a helloworld web app. Which is a common practice among Spring developers. Hehehe…

“It is best to program to interfaces, rather than classes. Spring reduces the complexity cost of using interfaces to zero” why it is best? what cost? yeah… Eclipse can “extract interfaces” if you want…. in compile-time!

“JavaBeans offer a great way of configuring applications” agreed! Great for anything involving pure data, indeed.

“OO design is more important than any implementation technology, such as J2EE” as pholosophy is to building houses. At some point, you have to deliver your software, so forget your idea of modeling the universe in your application… yeah, sorry guys, that’s impossible.

“Checked exceptions are overused in Java. A framework shouldn’t force you to catch exceptions you’re unlikely to be able to recover from” what??!!!! What’s next?”So frameworks should know how to divide by zero”. I think you will want to know what happened. This is worst than catching to e.printStackTrace(). Please, keep throwing and catching! Remember that try-cath-finally sentences are as important as if and for sentences for program semantics!!

“Testability is essential, and a framework such as Spring should help make your code easier to test” yeah, it is essential. Any framework should!

Bye! Keep keeping it simple, guys!

Maybe it’s a good idea to start introducing Spring in a more stable stage of the development in such a case.

I have heard more times about failed or out-of-date delivered Spring-based projects cases than successful ones (small ones). In most of these cases, people used Spring in early stages of the development, when they don’t really needed the solutions or flexibility Spring provides.

The real problem is when customers suffer this. They mistakely group plain Java development with Spring development and start preferring other technologies: php, .NET. So sad, since I think Java could do anything those technologies can do and much much more (including things they still can’t do).

Just another opinion. Regards.