> -----Original Message----- > From: George Allaman [mailto:[EMAIL PROTECTED]
> It occurs to me that an app developed in Turbine using Velocity > templates is not portable to any other application server. If > I had used > JSPs instead, I could port it to any app server that has a compliant > servlet container. Considering that very few ISPs support full blown > Apache HTTP server - Turbine - Tomcat - Velocity platforms, > this seems like a pretty big limitation. > I don't clearly see a strong point against Turbine's portability, but I see a misunderstanding. Turbine is just a servlet, in its implementation a standard was followed, and it can be deployed on any servlet container complaint with that standard: the Java Servlet API spec. The engine to render your Velocity screens it's already embedded, so there is no dependency on a specific container. As long as you are doing the packaging correctly, (including all the Velocity dependencies) you can drop your WAR file in any complaint container: Tomcat, Jetty, Weblogic, Websphere, Bluestone, etc. and voila! your pages should behave the same everywhere. On the other side, with JSP pages you don't have that much of a choice, you depend on the behavior of the container's page compiler, and some times that can lead to problems: bad performance, unexpected page layout, and finding those bugs is hard and time consuming, this argument lead me to skip JSP. Struts has some overlapping with Turbine, in their architecture both follow the MVC pattern, and their GUI concepts are similar: Actions, Events, Screens, Form validation, but Turbine goes the extra mile in terms of additional functionality and services like: Torque, Components, free Services, XML processing, etc. this functionality is out of the Struts scope. Rogelio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
