Rick has posted 25 posts at DZone. You can read more from them at their website. View Full User Profile

What server-side Java web framework will be the next for 2008?

01.20.2008
| 41506 views |
  • submit to reddit

I agree that Struts 1.x is not dead.

Probably the reason is that Struts 1 is terribly simple to learn (I don't remember who told this, probably Ted himself, anyway notice that this sentence is not mine ). Every other framework has its own point of view, with different capabilities, different approaches and a various way to say that their product is "the best".

Sincerely I would like a framework that has the power of Wicket, the simplicity of Struts 1, the elegance of Struts 2, the configuration scheme of Mentawai, the conventions of RIFE, the "standardness" and the paradigm of JSF, the approach of Spring WebFlow, the glue of Seam. Maybe it's Ruby on Rails
--A

Rails? Maybe. Probably not though.

Rick,

My two cents.

JSF appears to be gaining some market share. If you consider the fact that Oracle had integrated tools with their IDE and has been actively marketing JSF. I tech reviewed the new SCWCD for Sun Microsystems and there is a lot of JSF involved with the certification. So industry support helps, but does not enforce adoption.

Struts. I have always been a fan. I am using Struts 2 but I am also extending Spring framework. Using the Struts 2 controller with all of Springs offerings. That has provided some solid foundations.

Then there is Spring itself, controller and all. I really see this being a large market leader in the future. Especially seeing large consulting firms, (wish I could drop names) implementing Spring solutions for multi-million dollar contracts. This will leave a lot of Spring framework code out there to be maintained by someone.

I think most importantly all these frameworks have value. Or there would not be some many folks using, playing, adopting, and implementing. I really focus on what the frameworks have to offer and what the implementation really needs.

If I go with the gut...I would put Struts 2, JSF, and Spring (MVC) at the top.

The real value comes with maintenance. How readily available are resources to hire. If you look on Dice you can put in the framework and see the demand. When the dust settles you will want to build something that can be easily maintained at an affordable price.

Just my opinion.

RE: I use JSF and Spring MVC frequently. I would put Struts 2, JSF, and Spring MVC at the top as well.

Spring + Hibernate + ACEGI is a powerful combination. We've been using this for the past 18 months as a back-end with Adobe Flex on the front-end.

--Z

I’m seeing an uptick in business for JSF, primarily from larger corporations. Other than that, I’d say the big names these days are Grails and GWT. GWT, because of Google’s marketing muscle, is getting a lot of mindshare. I don’t know how that’s translating to actual jobs, though.
--K

Good to hear.

Most work I have seen centers around Struts 2.0, JSF, or Spring MVC.

Although I am starting to see a bit of Adobe Flex as an alternative to Ajax-infused views.
--S

Adobe + Flex with a Java back end seems to be something we run into every now and then as well. It seems like a good stack.

I don't think there will be one new big framework like Struts was. Nowerdays people can pick the framework that suits their specific needs.

The most populair frameworks today are JSF (component based) and Spring MVC (request based). But modern developers need to feel confortable with multiple frameworks IMHO because different projects suit different webframeworks.
--R

It is not like the good ole days eh? Everyone used Struts or their own custom request framework. Now there are real choices and some of them are quite good.

rick hightowercto of arcMindbloglinkedin

Published at DZone with permission of its author, Rick Hightower.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)

Comments

kent tong replied on Tue, 2008/02/12 - 2:46am

I am teaching a course on both JSF and Wicket. All the students joined the course to learn JSF and had never heard of Wicket. After learning both frameworks in the course they were asked which one they would use. 4 chose JSF and 3 chose Wicket. The rest didn't respond.

Ha Vo replied on Sun, 2008/04/06 - 10:54am in response to: kent tong

Kent, if you were to chose one of these choices and you knew that a lot of the devlopment had to be done by rather junior offshore developers who will be lead by seniors. Which one would you chose? I guess I'm asking what alternative can better be learned and controlled in an offshore model.

 Thnx for the reply

kent tong replied on Sun, 2008/04/06 - 9:23pm in response to: Ha Vo

In my opinion Wicket is much easier to learn and use than JSF. It also contains a built-in efficient unit testing framework which should be a major plus in an outsource model. Of course, juniors often don't write testable code, so having a unit testing framework alone is definitely not enough; mentoring is very much required.

Gerd Ziegler replied on Fri, 2008/11/07 - 7:28am

For those who like the simplicity of Apache Velocity theres a framework out there at www.ztemplates.org with form ajax support. For short intro take a look at introduction to ztemplates from Lunatech Research.

Ghanshyam Baheti replied on Sun, 2008/12/07 - 12:09am

Hi, Probably I may not be Ideal person to sure which framework has demand or big buzz for future days , but like to share some of my experience of working on Struts, Spring, wicket and JSF.

Spring is most suitated framework for Buissness logic layer and widely used with Integration with another frameworks like Struts,Wicket,JSF and.,,lab..la. So Spring is Common part with when we design most of the applications. So obiviously I feel its widely used. Also recently Spring Framework 3.0 is released with further features. go for more detail for my blog for this or spring official site. So Obiviosly spring is in demand I feel.

Here now question remains which one from Struts, Wicket and JSF.

Struts:- People are posting about it from 1995. so google have lot of stock! we know struts is no more. So less chances of use in new application devolpment. It is coming with struts 2 as well needs to be take into picutre.

Wicket:-Wicket is all about simplicity. It is Swing for Web Applications. There are no configuration files to learn in Wicket. Wicket is a simple collection of components. In Wicket, your web applications will more closely resemble a Swing application than a JSP application. If you know Swing, yes you know most of the Wicket!
None of the existing frameworks are appealing to me in terms of quickness, ease of development, easy to understand etc.

JSF:- It is another framework on which started to work recently. most of the Drag and drop devlopment is provided and looks very good. I see its growing widely. Still I need to learn lot in this, you can add here.

I missed here about other frameworks as i don’t have much Idea about them. you can make valuable addditions for us.

Rick Hightower replied on Thu, 2009/01/15 - 4:36am

It has been a year. Is there any current insight into this topic?

Bruno Vernay replied on Mon, 2009/02/16 - 4:45pm

I worked on a document about Web Frameworks. I would like to post it on JavaLobby. I would  remove the long list of framework and if you have other remarks, I would be curious to see what people think.

Thanks

Bruno

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.