RE: architecture
MichaĆ Mosiewicz <[email protected]> Mon, 7 Sep 2009 11:55:27 +0200
| Newsgroups | gmane.comp.java.open-symphony.webwork |
|---|---|
| Message-ID | <009c01ca2fa1$559049c0$00b0dd40$@pl> |
Choosing between Struts or JSF is a shallow problem view. It's like deciding between diesel or gasoline when buing a car. For me it it really a secondary decision although I like modern turbodiesels. However for real vehicle performance it's wiser to make decisions on more factors than just those. I'm not meaning to start wars, I prefer JSF, but JSF itself doesn't solve much yet. So I use JSF + Facelets + Seam + Spring. Other layers depends on the project type. Note that learnability doesn't necessarily mean productivity. IMHO struts application tend to be a little bit easier to understand because it's processing model is simpler. JSF promotes better programming patterns but is more sophisticated. I must admit that when JSF appeared on the scene it lacked productivity. We produced struts or webwork website much faster. However after Facelets, Seam and numerous JSF based frameworks and components arrived JSF's productivity jumped over Struts. -- Mike -----Original Message----- From: measwel [mailto:[email protected]] Sent: Sunday, September 06, 2009 7:25 PM To: [email protected] Subject: architecture If you were to start a new webapp project right now, what technology would you choose? The general requirements are: - Application has to be able to handle 1000+ concurrent users. - New developers must be able to learn the technology quickly Would you choose: Struts 2.1.6 or JSF 2.0 or maybe something else? <cut>