[Springframework-developer] Another TSS article

[Trevor C. <pr...@se...>]

Patrick's blog has been posted on TSS, so maybe another discussion will
start (the previous one on Rod's article seems to have died down, but maybe
it's just the weekend).  I read the comparison between Spring/WebWork he
wrote, and he actually seems to have spent a good amount of time/thought on
it, so take a look.
http://www.theserverside.com/home/thread.jsp?thread_id=21962

As far as the actual comparison goes, I think he did a fair job.  Spring
seems to come out ahead, and he lists our "weakness" (or areas where Webwork
is superior in his opinion) as:

- more flexible component lifecycles (request, session or application)
- simple configuration (which he specifies as "For a small number of
frequently used components, Webwork will require less configuration")
- more IDEA refactoring friendly

I think he's definately right about the "IDEA refactoring friendly" which I
translate as IDE-friendly (which would include Eclipse).  We've already
discussed our desire to have plugins in the future, so this isn't an unknown
issue.

As far as simple configuration, I haven't used WebWork2, so I'll take his
word for it.  Having introduced a number of developers to Spring I can
accept this (although I didn't have problems), although I wonder if it
applies to larger projects as well.  I'll be posting about this on TSS to
find out.

As far as "more flexible component lifecycles", maybe someone else can
comment (on list or on TSS), since I am unfamiliar with how WebWork
specifies it's cycles.  Generally I just use Spring for configuration,
request/session scoping is handled inside each controller.

Trevor