It will be more fruitful to tell us the specific reasons why you chose Turbine over Struts.
A few years back, when I had to make a choice between the two, I chose Turbine for the following reasons: 1. Flexibility to choose between different presentation formats: Velocity, JSP, etc. 2. The service framework. 3. Vast array of ready-to-use services - security, xml-rpc, jndi, logging, etc. 4. Object relational database - torque 5. A set of useful utilities - exception handling, form validation, email, parameter parser, etc. However, when I look at Struts now, I do not see Turbine having much of an edge over it. Struts now allows you the option to use Velocity as a template. Its no longer tied to JSPs only. You can use OJB as an OR tool with it. It also has a large set of useful utilities including form validation. Plus it has excellent docs and a large user base. Frankly, in my opinion you could not go much wrong in choosing either one as a framework for developing web-applications. ----- Original Message ----- From: "Eric Emminger" <[EMAIL PROTECTED]> To: "Turbine Users List" <[EMAIL PROTECTED]> Sent: Friday, March 21, 2003 10:08 AM Subject: Re: A database-based forms reports tool > Amin > > > What do u'll think bout struts in respect to turbine? > > Before deciding to use Turbine, I looked at *many* options, including > Struts. I chose Turbine because it seems to be the best all-around. So, > I think Turbine is better than Struts, at least for my applications. > > Eric > > > --------------------------------------------------------------------- > 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]
