You make the decision Velocity/Turbine vs. Struts/JSP

Jon, http://jakarta.apache.org/velocity/ymtd/ymtd.html I read your comparison of Turbine/Velocity and Struts/JSP and although you state it your aim to be "fair and unbiased", I think you failed since most of your examples, although sytanctically correct, were poor examples of the use of Struts a

Re: You make the decision Velocity/Turbine vs. Struts/JSP

Yea! Great feedback! I will reply in more detail soon. -jon -- If you come from a Perl or PHP background, JSP is a way to take your pain to new levels. --Anonymous

Re: You make the decision Velocity/Turbine vs. Struts/JSP

Niall, This is *excellent* feedback. I really appreciate it and look forward to working with you on this. My replies are included below. I hope you enjoy. I am currently queuing up a bunch of responses so that I can go through and update the document with feedback like yours. on 3/4/01 11:55 AM

Re: You make the decision Velocity/Turbine vs. Struts/JSP

I'm going through the document and making some changes based on yours (and others) suggestions and I have a question: on 3/4/01 11:55 AM, "Niall Pemberton" <[EMAIL PROTECTED]> wrote: > I read your comparison of Turbine/Velocity and Struts/JSP and although you > state it your aim to be "fair and

RE: You make the decision Velocity/Turbine vs. Struts/JSP

gt; Cc: [EMAIL PROTECTED] > Subject: Re: You make the decision Velocity/Turbine vs. Struts/JSP > > > I'm going through the document and making some changes based on yours (and > others) suggestions and I have a question: > > on 3/4/01 11:55 AM, "Niall Pemberton&quo

Re: You make the decision Velocity/Turbine vs. Struts/JSP

helps. -- Martin Cooper - Original Message - From: "Niall Pemberton" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, March 04, 2001 11:55 AM Subject: You make the decision Velocity/Turbine vs. Struts/JSP > Jon, > > htt

Re: You make the decision Velocity/Turbine vs. Struts/JSP

A question I have... is it feasible at all to use Velocity as the presentation mechanism with a Struts MVC framework? Regards, James W. -- This e-mail is from Cards Etc Pty Ltd (ACN: 069 533 302). It may contain privileged

Re: You make the decision Velocity/Turbine vs. Struts/JSP

I think it might be. Basically, Velocity renders the output, and passes it back. When used with a WebApp, the Velocity engine gets wrapped in a servlet, which pipes the output to the browser. From Strut's viewpoint, it wouldn't be any different than rendering a PDF or GIF. You just pass null back

Re: You make the decision Velocity/Turbine vs. Struts/JSP

[EMAIL PROTECTED] wrote: > A question I have... is it feasible at all to use Velocity as the > presentation mechanism with a Struts MVC framework? > The simple answer is "of course". The mechanism can easily forward to a servlet that displays the appropriate Velocity template, or your Actions

RE: You make the decision Velocity/Turbine vs. Struts/JSP

> > But, the point of what I am trying to say (and I will try to > clarify it > further in the document) is that by using Struts and JSP there is *NO* > enforcement that requires you to not use scriptlets. > [snip] > Putting Struts on top of JSP doesn't fix the warts in JSP. It > simply hides > th

Re: You make the decision Velocity/Turbine vs. Struts/JSP

On Sun, Mar 04, 2001 at 08:11:31PM -0800, Martin Cooper wrote: > Niall's revised example is *almost* right. Here's a fixed version of it: > > > Hello > > > <% if (request.getParameter("name") == null) %> > Hello World > <% else %> > Hello, <%= request.getParameter("name") %

Re: You make the decision Velocity/Turbine vs. Struts/JSP

So far, the arguments have been based on whether it is better for the page designer or Java developer. How about performance? IHMO, it would be interesting to find out the timing for each of the three approaches. I would agree with the Velocity's author that JSP taglibs is no much better than Cold

Re: You make the decision Velocity/Turbine vs. Struts/JSP

On Tue, Mar 06, 2001 at 01:15:34AM -0800, Wong Kok Wai wrote: > So far, the arguments have been based on whether it is > better for the page designer or Java developer. How > about performance? IHMO, it would be interesting to > find out the timing for each of the three approaches. > I would agree

RE: You make the decision Velocity/Turbine vs. Struts/JSP

http://www.multitask.com.au/NetRexx.nsf - Forwarded by dIon Gillard/Multitask Consulting/AU on 09/03/2001 01:32 AM - RE: You make the decision Velocity/Turbine vs. Struts/JSP > > But, the point of what I am trying to say (and I will try to > clarify it > further in the document) is that by usi