- This topic has 89 replies, 68 voices, and was last updated 15 years, 8 months ago by
.
-
Posts
-
At some point if the user requests are there. Struts 2 is Shale right? The framework built ontop of JSF?
Strtus 2 is not Shale. Shale split off. Struts took the WebWork code and will release it as Struts 2.
+1 for struts 2, may be it will be the trigger to finally see some support toward template engines like Freemarker and Velocity…
Struts 2 gets my vote also: +2 (we have 2 licenses)
The demand for Struts2 (which is not even released yet) appears to be pretty high
if you include all the WebWorks votes the past few years.Struts 2 release is in it’s final stages and should be official soon. I really hope there is support for it soon because I tried to get a HelloWorld up and running and failed miserably. The wiki is way to vague.
I want to be level with everyone here, MyEclipse has never been a product that just jumps on new technology as it comes out of the gate, we are completely user-request driven. So if tommorow, half our user base demands Struts 2 support, we’ll add it. On the flip side, if 3 of our users are demanding it, and everyone else is demanding Spring/MVC/WebFlow support we will work on the Spring stuff and pass on the Struts 2 work.
This approach has always allowed us to grow and be successful with our users while addressing most all of their needs… unfortunately from time to time there are cool technologies that may not get addressed by us directly because our management team has to do what is best for the company, and the cost of developing a new feature (develop time/salary) and then factoring in the years of enhancements and bug fixes that will go into that feature after it’s release can get really high.
So if you don’t see Struts 2 support comming from us soon and you need it, good ways to get our attention is to have your company request the feature for a large amount of subscriptions or gather a lot of folks together to demand it.
I hope that helps.
I think there needs to be a more formal process for shaping the future of MyEclipse. How do you determine when “half the users have requested Struts 2?” I know that my firm plans to migrate to Struts 2 and I have been expecting that MyEclipse would evolve the Struts 1 support to include Struts 2 without customer intervention. What is the process for deciding you have worked “long enough” on supporting a particular technology? Hopefully a competing technology showing up does not automatically halt work on your current included support.
I’m sure this is an interesting problem, and I am merely asking as interested customer.
Thanks,
Scott StanlickScott,
It’s a good question. We’ve always been a customer driven product which is why we offered support for things like Struts long before many other competators ever did; our customers demanded it. I don’t think we will be changing that strategy because there are just too many technologies out there to start targetting the “big ones” (not sure how we would decide that besides user demand).That being said we aren’t waiting for 1/2 our users to demand Struts 2 or Wicket or Tapestry 4 or JEE 5 or JPA or any of the any other technologies, we just wait for a serious level of demand from our users to popup before we look into a technology. For example Facelets has been on our list for a while and Maven2, the request threads for those are quite long. Wicket, while a great technology, only has 3 or 4 requests. Struts 2 isn’t much more than that at this point and then we have the Struts/Shale thing as well that has a few requests.
We need to be picky with what we attack, because everything we attack is a ongoing commitment. Just because we deliver Struts 2 support, you guys will want bug fixes and enhancements and feature additions for years to come. When add all that up, the support requirements and everything else that goes into a big feature like that, it gets very very expensive. So we need to pick wisely.
So the take away message here is keep requesting. If you get loud enough, we’ll succumb to your wishes 😉
