I"m not real familiar with Turbine either... But based on your description of it, you point out that it does not use JSPs for view, which Struts does. I"m curious, what does Turbine use/recommend for creating the view? Surely it does not reccommend putting all of the view into a servlet???
FYI, Stuts does NOT encourage the use of lengthly scripts and business logic inside the JSPs. JSPs are used as the view components, while servlets serve as controllers, and the business logic should be placed in beans. Tim --- Oki DZ <[EMAIL PROTECTED]> wrote: > On 04/23 15:20 Joel Rees wrote: > > So, how do you think Turbine compares to Struts? > I've been looking at both, > > but my colleagues prefer the designated standard > track. > > I can't tell; never been used Struts (but I've taken > a look at: > http://www.mail-archive.com/[email protected]/msg00495.html) > Turbine is a template-based web apps framework, and > mainly uses servlets. > It seems that Struts is too, but it uses JSPs for > the presentation (view). So, > I think if you like to put Java codes in the > scripts, then Struts would be for > you. But if your scripts (for presentation) are not > so complex and you like to > put your business logic on servlets, then I believe > that Turbine is for you. > > In a sense, JSPs are templates too, but they put > (you could put) lots of > business logic in them. Turbine doesn't want you to > do so (presentation is > presentation, only some if's are allowed :-); if you > need to do templating a > lot, you can use the templating support (ie: > Velocity), but if not, you can > stick to just servlets (and ECS, maybe). > > BTW, what is the "standard track" in web > applications building...? > > Oki > > -- > To unsubscribe: > <mailto:[EMAIL PROTECTED]> > For additional commands: > <mailto:[EMAIL PROTECTED]> > Troubles with the list: > <mailto:[EMAIL PROTECTED]> > __________________________________________________ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
