This is the mail archive of the xsl-list@mulberrytech.com mailing list .
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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@XMLCities.com] > Sent: Wednesday, January 30, 2002 5:21 AM > To: XSL-List@lists.mulberrytech.com > 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
Attachment:
smime.p7s
Description: application/pkcs7-signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |