- This topic has 89 replies, 68 voices, and was last updated 15 years, 8 months ago by
.
-
Posts
-
“the whole industry seems to be moving to JSF solutions. “
Really? You think so? I’ve been working as a contractor in the UK for the last 3 years, in a number of different companies, almost exclusively on web application projects and its all been on Struts or WebWork (or on some proprietry nonsense, but we won’t go there). In my experience I’d say struts has much deeper market penetration the JSF (just have a look on Jobserve for JSF jobs compared to struts) and because of that companies are going to be more inclined to move to Struts 2, where there is a migration path, rather then to a totally different framework that would require everything to be rewritten.
So, yes please for struts 2 support.
(+2, I’ll be getting another license in the new year)Tom
@tomalyle wrote:
“the whole industry seems to be moving to JSF solutions. “
(…) struts has much deeper market penetration the JSF (just have a look on Jobserve for JSF jobs compared to struts) (…)
This is not a valid comparison, as JSF (like EJB) must not be mentioned in a job description: it is part of the standard Java plattform. A Java EE developer of course has knowledge of the most important Java EE technologies.
And why is there such a huge demand for facelets (see topic “Facelets support”) and so little for struts 2?
−1 for Struts 2
And why is there such a huge demand for facelets (see topic “Facelets support”) and so little for struts 2?
This is a quandry. Our corporate customers have never demanded Facelets support, and continue to demand Struts (not 2, but 1) support. Then our community demands Facelets support, Struts 2, Seam and EJB3.
It’s interesting to see but not too surprising, corporations can’t throw out legacy apps any time soon, and community developers tend to be more cutting edge and then take that technology to work with them as they roll out new projects. It’s still interesting though.
@support-rkalla wrote:
It’s interesting to see but not too surprising, corporations can’t throw out legacy apps any time soon, and community developers tend to be more cutting edge and then take that technology to work with them as they roll out new projects. It’s still interesting though.
We must do so. If not, we will be replaced by some Ruby on Rails developer in the not-so-distant future. Java EE development must become much faster, or it will follow Cobol’s fate.
I’m curious to see what Sun pushes this year at JavaONE. They did a great job educating folks about EE 5 last year and there is a lot of potential there, but I agree, there is more work to be done.
@support-rkalla wrote:
I’m curious to see what Sun pushes this year at JavaONE. They did a great job educating folks about EE 5 last year and there is a lot of potential there, but I agree, there is more work to be done.
IMHO Sun should focus on JSR 299 (Web Beans). If this develops on normal JSR speed, there won’t be anything usable before 2010 …
@support-rkalla wrote:
I’m curious to see what Sun pushes this year at JavaONE. They did a great job educating folks about EE 5 last year and there is a lot of potential there, but I agree, there is more work to be done.
Indeed, there is a lot more work to be done. JSR 299, which the poster belows mentions, is indeed one of the more interesting of the new developments. Since this one is closely alligned to Seam, it may be extra worthwhile for you guys to start with Seam support (if time allows). Part of that work may be reused for JSR 299 in the future.
One aspect that refrains me from looking at new Java EE developments (i.e. past EE 5) is the fact that it always takes ages for support to catch up. Java EE 5 has been declared final for some time now, and most major app servers (Jboss, Bea, even Tomcat) are yet to come with their support in a stable release. Editor support is lacking too. MyEclipse seems to be a pretty agile team, but they still don’t support the bulk of the new EE 5 syntax (e.g. JSP 2.1, Taglibs 2.1, JSF 1.2, etc). Worse yet, not even JSP 2.0 is 100% supported at this time.
In my personal opinion it would be best to solidify support for standard techniques first, before moving on to anything newer than that.
MyEclipse seems to be a pretty agile team, but they still don’t support the bulk of the new EE 5 syntax (e.g. JSP 2.1, Taglibs 2.1, JSF 1.2, etc). Worse yet, not even JSP 2.0 is 100% supported at this time.
It’s been a thorn in our side as well as other tool providers. EE 5 was such a huge spec to support is all would be a product in and of itself, that’s why it’s taking everyone so long to catch up. Everything from file structures (gotta throw out the old grammars and lexers) to the expression languages (woops gotta throw out the evaluaters) to EJBs (all annotations and JPA) has changed… in a lot of ways it’s like 4 new frameworks came out all at the same time. But that’s all the bad news, the good news is that the support is coming, there is no avoiding it. Standards need to be supported and will get supported. We aren’t going to roll out 2nd rate support though, which is why we aren’t throwing in a simple wizard and calling it a day. We realize that “EJB3 support” means a heck of a lot more than just some anotations and a bunch of “Next, Next, Finish” wizards.
We are interested in Seam and this spec you guys mentioned I wasn’t aware of either, I’ll need to get some time with it to see what it is all about.
+1 for Struts2 too.
I really appreciate the Struts Flow Overview, and I miss it terribly now that we switched to Struts 2.
Keep up with the great work!
alexis
Looking for a product for my company that is a Struts 2 editor, I find that myEclipse is the closest thing availble on the market that work. Just needs to be struts 2 and potentially we would be on a winner, with potentially 20+ subscriptions.
So yes. Add a vote for struts2 from me.
Riyad,
I have been a happy user of MyEclipse for a few years and would love it if you could make a commitment to Struts 2. I understand your position and hope you get enough requests to move forward.
Thanks, Brian
