views:

122

answers:

2

Earlier i worked on Struts 1. Struts 2 seems own good design, comparatively fast, fun, and professional. But I could not search who is using Struts 2. Do anyone know which web applications are using it? Any other advice about adopting it for new web ventures?

Please also share your personal experience with it, if you have worked on it!

Thank you so much.

+1  A: 

I migrated a medium-size webapp from Struts to Struts2.

If found Struts2 to be a very different framework (it is actually a merge-update of Struts and Webwork, with much more from the later).

I tend to like it, I consider it much more straighforward, elegant and easy to use than the old Struts (man, I'd hate to return to that one...). It is also relatively easy to learn, and there are a few good books.

On the downside: it's not easy to get confortable with the ONGL syntax + value stack thing, the documentation in the website is a little anemic...

And more important: the Struts2 project does not seem to enjoy very good health IMO. Not much depelopment buzz, little community. The future does not look so bright - other java web frameworks arent' much better, though...

leonbloy
Basically I want go for SpringMVC or Struts2. JSF is slow as compare to these. So how do you compare the SpringMVC with Struts2? What one should adopt?
Asif Shahzad
I haven't used SpringMVC, so I can't decide. I believe they are even, in most respects (similar strengths, popularity, philosophy, prospects) so it's not a very critical decision. Flip a coin? :-)
leonbloy
Thank you so much, leonbloy!
Asif Shahzad
+1  A: 

I'm part of a team that developed a middle size web-app in Struts2 since it was the" new and improved" Webwork. Back in the day, Struts2 had a more complete arquitecture and tag library that Spring MVC. (Although we used Spring as IOC Container and its suport of Hibernate)

I wouldn't say Struts2 is bad but there were some itches I could not scratch.

  • It's power can be complex to handle (The use of interceptors for anything from populating an action to deciding what to do with an action result)
  • Struts2 configuration offers flexibility but it was not really needed in our case and it became somewhat cumbersome to mantain
  • Documentation was a bit dry and, in the case of the AJAX tags, there were incorrect or incomplete descriptions (This might have changed...)
  • Once you start writing a complex application, Struts2 is not that fast

For our next project I'm not considering Struts2 because of the reasons given above and mostly, I've seen very little activity in the project in the past two years. (We are considering Spring MVC, JSF2 among others)

madth3