I believe one of the important reasons why Struts is still going strong after 5 years is that it is very efficient and has a relatively low learning curve than other component-based frameworks such as tapestry,JSF and so on. With tools such as Creator, JSF apps might be easy to start. But to write a non-trivial JSF app, it requires a deep understanding, which I believe is harder to grasp than Struts.
The great thing about Struts is that it doesn't try to hide the underlying request/response servlet model from your code. JSF can be a win if you have good IDE support and a rich set of components to work with. But if you roll your own, it's hard to wrap your mind around all the things you need to do in order to make a stateless protocol look like a stateful GUI component framework.
Especially now that Javascript is cool again (AJAX), we can start building more stateful UI components, with a clearer separation between stateful client-side components and sorta-stateless (well, there's that HttpSession thing) server-side ones.
-- Bill -- Bill Schneider Chief Architect Vecna Technologies, Inc. 5004 Lehigh Road, Suite B College Park, MD 20740 [EMAIL PROTECTED] t: 301-864-7594 f: 301-699-3180 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
