Subject: RE: [xsl] Need 3 good reasons why XSLT is better than JSP+Velocit y From: "Kovach, Dave" <dave.kovach@xxxxxxx> Date: Thu, 31 Jan 2002 00:23:33 +0100 |
Its not a valid debate -- ASP/JSP vs. XSLT... you can finely augment an ASP/JSP web environment and do all XSLT processing on the server - it actually works beatifully(as long as you have Jeni or Michael Kay's book handy)... And you can have REALLY complex input - like any other application... (a framework pre-built or built on your own helps this of course) Just more thoughts, David Kovach SAP Labs Palo Alto, CA -----Original Message----- From: Joshua Allen [mailto:joshuaa@xxxxxxxxxxxxx] Sent: Wednesday, January 30, 2002 2:26 PM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Cc: WLagrone@xxxxxxxxxxxxx Subject: RE: [xsl] Need 3 good reasons why XSLT is better than JSP+Velocity I don't think XSLT is "better" than JSP for creating web pages, just different. Here are some scenarios where XSLT makes sense: 1. The data is being transformed directly to presentation content, and input complexity (form submissions, processing of submit results, etc.) is minimal. 2. The site is content-oriented 3. The devs have some good tools (excelon, xml spy, etc.) for designing transforms Here are some reasons to stick with JSPs: 1. The data needs to have "business logic" processing done as it's used to generate a web page -- things like calling Java classes (or COM components, etc.) 2. The developers need significant control over how data gets cached in-RAM on the web servers (currently, no XSLT-serving frameworks that I know of make it easy to say which stuff should get cached and which not) In any case, the learning curve argument is a legitimate one. Some of the tools available now make that less relevant, but the difference between ASP/JSP and XSLT in many situations might not be worth forcing devs to switch from one to the other. After all, ASP/JSP are template-oriented web page creation languages as well.. > -----Original Message----- > From: Wes Lagrone [mailto:WLagrone@xxxxxxxxxxxxx] > Sent: Wednesday, January 30, 2002 5:21 AM > To: XSL-List@xxxxxxxxxxxxxxxxxxxxxx > Subject: [xsl] Need 3 good reasons why XSLT is better than JSP+Velocity > > Wondering if anyone could shed light on a debate I've been having with > web developers. > > If the source content for my web site is a stack of XML files, XSLT > seems like the obvious choice to assemble, format and generate the > output XHTML pages. > > But many web developers tell me that they'd rather use Velocity > templates in conjunction with JSP to accomplish the same thing, whether > the source content comes from flat XML files, an XML repository, or an > Oracle database. They know Java, they argue, so why bother with XSLT? > > So I'm looking for three good reasons why they're wrong. > > Thanks, > > Wes > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Need 3 good reasons why X, Hunsberger, Peter | Thread | RE: [xsl] Need 3 good reasons why X, Hunsberger, Peter |
RE: [xsl] Need 3 good reasons why X, Joshua . Kuswadi | Date | RE: [xsl] Need 3 good reasons why X, Kovach, Dave |
Month |