://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 using Struts and 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
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
http://jakarta.apache.org/velocity/ymtd/ymtd.html
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
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
: 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
Niall's revised example is *almost* right. Here's a fixed version of it:
html
headtitleHello/title/head
body
h1
% if (request.getParameter("name") == null) %
Hello World
% else %
Hello, %= request.getParameter("name") %
/h1
/body/html
The difference is that in order to print
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
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
[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 forward mechanism can easily
forward to a servlet that displays the appropriate Velocity template, or
your
10 matches
Mail list logo
