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] |
Yeah, in my opinion this approach makes the most sense. Skills with template-oriented procedural frameworks like PHP/ASP/JSP are widespread and easy to pick up. Using an XSLT presentation framework along with one of these is probably the quickest path to productivity. There will still be a resistance by some people to learn two different languages, so we have to be realistic about that, but that's a place where tools (and good books) can help. > -----Original Message----- > From: Kovach, Dave [mailto:dave.kovach@sap.com] > Sent: Wednesday, January 30, 2002 3:34 PM > To: 'xsl-list@lists.mulberrytech.com' > Subject: RE: [xsl] Need 3 good reasons why XSLT is better than JSP+Velocit > y > > To keep this focused on XSLT... > > You CAN handle business logic in an ASP or JSP or plain > SERVLET environment and still use XSLT and XML for building > a kick-butt presentation engine framework... it all works > really well together - cause xml and xslt (because its > xml) are so invisible and transparent to use and put into > play... > > David Kovach > SAP Labs > Palo Alto, CA > > -----Original Message----- > From: Bryan Kearney [mailto:bk@avolent.com] > Sent: Wednesday, January 30, 2002 2:56 PM > To: 'xsl-list@lists.mulberrytech.com' > Subject: RE: [xsl] Need 3 good reasons why XSLT is better than > JSP+Velocit y > > > Here is another... > > How cheaply you can get folks who know it. This is a valid business reason > to stick with JSPs. They teach it all over. > > -- bk > > > > -----Original Message----- > > From: Hunsberger, Peter [mailto:Peter.Hunsberger@stjude.org] > > Sent: Wednesday, January 30, 2002 3:40 PM > > To: 'xsl-list@lists.mulberrytech.com' > > Subject: RE: [xsl] Need 3 good reasons why XSLT is better than > > JSP+Velocit y > > > > > > > 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.) > > > > I would argue that if you really have this requirement and > > you really can't > > figure out how to push it out of the presentation layer (with > > XML/XSLt it's > > usually pretty easy) then you may have a need for XSLt > > extensions. I do not > > think that it is a reason to stick with JSP's. > > > > Peter Hunsberger > > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > > 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] |