1) In the process of doing one now, Struts 1.2.7. 2) Don't know enough about other frameworks, but for now would stay away from component-based ones (JSF, Tapestry). Wicket and Stripes look interesting, but they're pretty green.
As an aside, the rest of the team I'm on was just trained (formally) this past year in Struts and other webapps are in Struts. To suggest a different framework at this point would be to commit seppuku, I suspect this is the case at many corporate shops as well. The business case to switch to a new framework has to not just be "better" (more productive, better features, etc), but orders of magnitude better for management to essentially abandon a prior decision. -ed On 11/1/05, Ted Husted <[EMAIL PROTECTED]> wrote: > On 11/1/05, James Mitchell wrote (elsewhere): > > I guess the big difference > > (for me) now is that I actually have a paying gig doing JSF/Shale, so > > there's more incentive for me. > > Which begs a query to the group: > > (1) Is your team planning a new web application project over the next > twelve months? > > (1a) If so, what web application framework do you plan to use? > > (2) Hypothetically, if you were starting a new webapp project, and for > some reason could not use a Struts framework (Classic, Shale, > OverDrive, Ti), what other framework would you want to use? > > > -- HTH, Ted. > http://www.husted.com/poe/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
