Big thanks to all who contributed to this thread. I would suggest a new thread on Struts vs. Turbine, and perhaps another on Velocity vs. JSP. Both of these topics are of great importance to those considering using any of these technologies, and I found the posts in this thread to be very illuminating. I do find Velocity templates much easier to write than JSPs, and more readable to non-Java programmers.

Forgive my ignorance about how easy Turbine is to port to any compliant servlet container. And thanks for showing me how to do it. I certainly did not mean to malign Turbine - I quite like it, especially now that I know it is portable to any servlet container.

I am still puzzled why Struts seems so much more mainstream than Turbine. I've never seen a job post asking for Turbine skills. For some reason I had the impression that Struts integrates better with J2EE but I forget where I got it.

What Turbine needs most, I think, is some kind soul to assemble all the documentation in one place where it is organized and easily accessed. In almost all cases, I've found the answers to my questions in the existing documentation or in the mail list, but damn, does it take a long time to find it! For instance, I could find nothing on how to port to environments other than the TDK. Of course this isn't a Turbine specific issue, but how was I to know that?

Unfortunately, because the product changes like all products do, the documentation gets out of date pretty quickly, so it needs to be kept up. Wish I could do it. If I understood Turbine, app servers, and servlet containers better I might, but my ignorance is pretty daunting.

--
George Allaman
Denver, Colorado
303 466 2114



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to