I have been reading 'Spring Recipes' and learning all about Spring 2.5 for the first time. I have read all about Spring JDBC, transactions, AOP and eliminating cross-cutting concerns...my problem is this: I still don't get it. I am waiting to see some problem that Spring is solving for me by making things easier and clearer but from what I have studied so far it just looks like Spring introduces twice as much complexity to solve the standard types of problems. And, the cross cutting concerns that you eliminate are replaced by Spring code which seems to hide logic and make things more obfuscated. Even the JDBC and transaction management seem much simpler and clearer to do with straight JDBC. Am I missing something? What is the real payoff here that Spring provides that I could not do otherwise? I am dying to hear at least one real world example that makes me say: "oh yeah? that is awesome!"
Can anyone offer me some clarity here? Thanks John -- View this message in context: http://www.nabble.com/Is-Spring-worth-it--tp21692769p21692769.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
