Some rebuttals -
* Spring MVC
Too flexible and customizable (could I say annoying?) but it doesn't offer a lot out of the box.
It is definitely heavily configuration based. I'm not sure what you mean by 'doesn't offer a lot out of the box'... if anything, Spring MVC is used by a ton of projects because it comes with Spring.
* Struts 2
Maybe Time has passed it away and should be kept in a museum.
I haven't used it a lot... I've heard that conceptually it's similar to Spring MVC (but Spring MVC has the advantage of being packaged with the rest of the Spring framework). The biggest problem is that Struts 1 was so popular - but Struts 2 was basically another project (WebWork 2) renamed Struts 2 and around the same time a lot of other frameworks were coming out. A bunch of people either stuck with Struts 1 or figured if they were going to learn a new framework, there was no real benefit of learning Struts 2 vs. some other framework. I think you mean Struts 1 rather than Struts 2 in your comment.
* Tapestry 5
Not even in my consideration.
Haven't used it - biggest complaints I've heard are changes between versions and slow release cycle. It's also a templating engine, which is conceptually different from request/response based frameworks (Spring MVC, Struts, etc.) and more similar (but not exactly) to component based frameworks (JSF, Wicket, etc.)
Liked it a lot but I can't digest the JFC/Swing over the HTTP thing.
Wicket doesn't use JFC/Swing... it's simply a component based web framework. I've heard good things about wicket (i.e. - that it's a better component based framework than JSF).
I invested a lot of time in it, so delicious and powerful but the lack of help from their web site and being a JSF enhancement framework were stoppers for me.
Seam is popular among a lot of projects because it's based around the 'standard' JEE
technologies (JSF and EJB as opposed to something like Spring), but actually makes them usable. :P
Sexy and breath taking but being a soooo client-concetrating and building the interface in the code were again a stopper for me.
Yes, it's client-concentrating... it's an AJAX based web framework. Lots of people like it because it's backed by Google.
The framework I use right now.
I like the simplicity and productivity of Grails but many important plugins aren't well documented (if any).
And there is the Groovy thing, there is some thing in the language I don't know what it is but I don't feel its power.
Some times I feel it is just a simplified syntax over Java's.
Grails is basically a framework similar to 'Ruby on Rails' but for Groovy instead. It's written on top of Spring and Hibernate. Not sure what the 'don't feel it's power' comment on Groovy was about... it's a scripting language with syntax similar to the Java language. The only complaint I usually hear about it is that it uses Groovy instead of Java.
Jobs trends show that the most wanted frameworks are: GWT, Wicket, Grails
I'm not sure where you're getting your job trends... It's going to be different by area, industry, etc. but I'd say that most projects are using either Spring (and Spring MVC for the web framework) or no 'framework' other than just JSF or JSP
. There are still a lot of old projects using Struts 1 (please no new projects in this, though...). All the other frameworks are in use to some extent but are dwarfed by these. Out of these I'd say GWT (because it's backed by Google) and Seam (because it's close to standard JEE) are used the most.