In my opinion this depends on the preferences of the developer and how
he likes to organize his code.
I never used Spring much. In the past I could never get used to the
XML configurations. I simply don't like it. I especially don't like it
in EJB2. Up to now I never had time to check out the Spring
annotations. What I do like are working function keys in Eclipse, esp.
F3 + F4 :-)
Am 27.01.2009 um 20:38 schrieb johnrock:
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.
Well, you cannot remove complexity, you can just shift it around or
move it to another place in your code. Spring, like any framework, may
hide some of the complexity and deal with it in a common, or
"standard", way. At the price of additional abstraction.
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?
Spring is just a framework you may want to use or not. The problems
which are addressed are the same everywhere: JEE, Spring, .Net, ...
The common developer out here has to solve business problems. The
technical issues are not his main concern, and usually don't play a
major role in the business model of his employer. Thus the big players
create frameworks/products/APIs which hide the common technical
problems as much as possible, in a more or less intuitive way. The
developer has a set of building bricks which plug together nicely and
help him to reach his goal as fast as possible: solve the business
problems.
I am dying
to hear at least one real world example that makes me say: "oh yeah?
that is
awesome!"
Right now I use EJB3 and JPA for the most part, along with a little
Spring (AECGI and some more) in the webapp. For the DI part to wire
the actions with the services and some external JAX-WSs: here runs my
own glue code, as my action doesn't care whether a service is a EJB,
WS or just a simple Java object I configured into the interceptor to
be injected.
Well. Everybody puts their pants on one leg at a time... Expect to be
unimpressed whatever you decide :-)
-Ralf
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
