Re: Taking a step forward in JAVA programming

From:

=?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>

Newsgroups:

comp.lang.java.programmer

Date:

Tue, 29 Jun 2010 20:38:49 -0400

Message-ID:

<4c2a9213$0$276$14726298@news.sunsite.dk>

On 29-06-2010 05:55, Arved Sandstrom wrote:

Arne Vajh?j wrote:

On 24-06-2010 05:30, Arved Sandstrom wrote:

I'm not going to recommend a web framework. I've used JSF and Struts a
lot, Spring quite a lot, and given Wickets a fair shake. I believe a
person can make any of them work, and of the two major players (JSF and
Spring MVC) I don't really see that one is better than the other. In
particular I don't buy any SpringSource claims that their approach is
easier than JSF...I don't think it's more difficult but it sure isn't
easier. For somebody with educational time to burn I'd say try
both...Spring MVC does have the advantage of being part of a whole
constellation of technologies.

Is Spring MVC really that popular?

There were a lot of hype some years ago when Spring
was red hot, but I believe the conclusion was that the
first versions of Spring MVC was crap. Later versions
should be better. But my impression is that JSF and Struts 1
are the big ones. And Spring MVC is just one out of many
in next tier (Struts 2, Wicket, Sling, Stripes etc.).

You're right, I dashed that off without thinking that much about it.
Here's a guy who has done some fairly thorough analysis
(http://www.thebuzzmedia.com/which-is-the-hottest-java-web-framework-or-maybe-not-java/),
and he has it that JSF is the clear leader, Spring MVC/Web Flow
considerably less popular than I thought, with Struts 1/2 being 2nd
place, Wickets being 3rd, Spring MVC/WF and Seam trailing in 4th and 5th
place. This article
(http://ozgwei.blogspot.com/2008/06/which-is-hottest-java-web-framework.html)
refines the same Google Trends analysis some.

That match better with my expectations.

In hindsight I suppose I'm not that surprised about the Struts 1/2
placing, but I am surprised that Wicket is that popular and Seam and
Spring aren't.

As a side note, despite articles like
http://www.thebuzzmedia.com/apache-wicket-powers-mobile-walmart-com/ I
am not enthused by Wicket. I think it's verbose, and I think that anyone
who believes that it's lightweight and clean hasn't built an equivalent
complex enterprise Java EE web app with something else like JSF.

Wicket has been hot for some time.

Maybe it has just been hype and it will go away.

But maybe it will stay around.

I think its existence is justified. It is somewhat different
from the rest of the frameworks that are relative similar.

Arne