> -----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 the presentation layer completely declarative
>
> The why not just write a servlet that instead for forward to
> display JSPs,
> looks up a different XSLT for display based upon the action
> class being
> requested ... and instead of having to pass all your data to the
> presentation servlet in beans ... you just transform your XML
> data using
> that XSLT. Seems to achieve the same goals and
> architecturally removes a
> layer if you're going to use XML at all. (Just servlet and
> XSL instead of
> Servlet, JSP, and XSL).
I think the real key to what you are asking is "if you're going to use XML
at all", or really, if your web app is XML-centric. Many (most?) web apps
with complex back end needs are not going to be manipulating their model
data in XML. That means that "instead of having to pass all your data to the
presentation servlet in beans", you would have to construct an XML document
(e.g. a DOM) to do that, for your approach to work.
Certainly, if your web app really is XML-centric, then there are numerous
other approaches that might work well. But if your model is already based on
beans (EJB or otherwise), then JSP and Struts provide a big boost in putting
your app together.
--
Martin Cooper
>
> ??????
>
> Any thoughts??
> Neal
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
