- This topic has 8 replies, 6 voices, and was last updated 18 years, 4 months ago by
.
-
Posts
-
STRUTS 1.0, 1.1, 1.2 are things of the past.
The current STRUTS mainstream version is 1.3 and the immediate future is STRUTS 2.
MyEclipse should integrate STRUTS 1.3 and STRUTS 2, because we don’t need a leading edge product locked on past technologies.
ZartC
MyEclipse will need to support struts 2 in the next few months! I am not sure at all why there is no support for it, since it will quickly have 10x the community of JSF and other web frameworks.
this is a must if MyEclipse plans to survive.
Jason,
Our users input is key to us. What are the key features in Struts2 that you are using in your applications that we need to be aware of when we are considering tooling (e.g. internationalization support? program flow? etc.)Also have you found developing with Struts2 to be faster/easier than with Struts 1/WebWork or do you think there is a ramp-up time there like there is with JSF or Tapestry?
Also what hiccups (if any?) have you had when deploying your Struts2 applications? For example app-server incompatibilities, debugging issues, library compatibilities, etc.
Hmm, Google Trends:
http://www.google.com/trends?q=%22struts+2%22%2C+%22jsf%22&ctab=0&geo=all&date=allNotice the blue curve at the far right corner… seems like a lot of ground to cover.
Hey there! So the JSF referred there on Google Trends are jet planes and we’re comparing them to Struts2! Very interesting comparison!
Ideally Struts 1.3 should’ve been out in 5.1 and Struts2 in 5.5, but it doesn’t seem either is on the roadmap!
For now, I suggest that 1.3 should SERIOUSLY be considered for ME5.5 even if it delays it a bit. People I know are having to NOT use MyEclipse because of incompatibility with 1.3.
