On 9/4/2002 at 9:47 PM Ted Husted wrote:
As alluded, the stxx extension does a nice job of this by integrating
with Struts. Though, I'd say the idea of a completely seperate servlet
(a la Velocity) sounds cleaner.
Why do you think this to be the case? If you do think that xml/xslt is the
As alluded, the stxx extension does a nice job of this by
integrating
with Struts. Though, I'd say the idea of a completely
seperate servlet
(a la Velocity) sounds cleaner.
Why do you think this to be the case? If you do think that
xml/xslt is the
winner in the long run (as do I,
If that's the perceived complaint, wouldn't it be better to
connect the
model data to the view using a sax pipeline rather than
passing around a
dom or dom-like object, or even worse, a String?
And the sax 'pipeline' (I assume you mean an InputStream?) is connected
towhat? If your
Donald Ball wrote:
On 9/4/2002 at 9:47 PM Ted Husted wrote:
As alluded, the stxx extension does a nice job of this by integrating
with Struts. Though, I'd say the idea of a completely seperate servlet
(a la Velocity) sounds cleaner.
Why do you think this to be the case? If you do
I see what your
I don't mean an InputStream, I mean a sax pipeline. sax is an
event-based
api for transferring xml data. In the typical mode, a sax generator,
typically a parser, is given a ContentHandler object on which
it will call
methods (startElement(), endElement() characters(),
There are a couple of frameworks out there that endorse this idea, and there's
certainly nothing in Struts that mandates the use of JSP. I think a person on this
list has implemented something exactly as you describe with Struts.
My .02:
1. XSLT is slower than JSP, varying upon the
We are finding Jaxen and Dom4j a quite effective match with XPath. We
are using it for handling tree menus with having an action just pass
back xml where the JSP checks the request header to see if the
transformation can be done client side, else we pass it through JSTL
tags server side. We
Subject: RE: Struts - vs XSLT (ASP.NET v. Struts)
There are a couple of frameworks out there that endorse this idea, and
there's certainly nothing in Struts that mandates the use of JSP. I think a
person on this list has implemented something exactly as you describe with
Struts.
My .02:
1. XSLT
-Original Message-
From: neal [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 04, 2002 4:29 PM
To: Struts Users Mailing List
Subject: Struts - vs XSLT (ASP.NET v. Struts)
Alright, so if the purpose of Struts and ASP.NET is:
1. To seperate code from content
2. Make
As alluded, the stxx extension does a nice job of this by integrating
with Struts. Though, I'd say the idea of a completely seperate servlet
(a la Velocity) sounds cleaner.
http://jakarta.apache.org/struts/resources/views.html
The Expresso/Struts framework also supports XML/XSL directly.
As Joe said, Struts doesn't mandate JSP.
A more appropriate comparison will be
JSP vs XSLT
In this regard, both are scripting-oriented languages.
Performance aside, I believe the selection is a matter of preference.
At 07:28 am 05-09-2002, you wrote:
Alright, so if the purpose of Struts
Mailing List
Subject: Re: Struts - vs XSLT (ASP.NET v. Struts)
As Joe said, Struts doesn't mandate JSP.
A more appropriate comparison will be
JSP vs XSLT
In this regard, both are scripting-oriented languages.
Performance aside, I believe the selection is a matter of preference.
At 07:28 am 05
12 matches
Mail list logo
