On 04/23 20:15 Timothy Fisher wrote: > 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?
The recommended way to create the view is by the templating support; it is done via (one of them is) Velocity; so basically, you'd have a template for defining all the fancy html tags, and then you'd have a servlet that makes use that template. In the template, you could define "script variables" that extract values from the servlet. > Surely it does not reccommend putting all > of the view into a servlet??? Of course not; that's not the way it is. You are encouraged to use the templates for displaying the views. > FYI, Stuts does NOT encourage the use of lengthly > scripts and business logic inside the JSPs. Well, it should be so... I think it boils down to a matter of preference; if you want to stick with Java (nothing but Java) even in scripts, then JSP would be your choice. But if you are horrified with all those JSP tags to learn, then Velocity templates could be a better choice. Sure, speaking about power, JSPs would be much powerful than Velocity templates, IMHO. > JSPs are used as the view components, while servlets serve as > controllers, and the business logic should be placed > in beans. I think you described it more clearly... Oki -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
