Actually, There's nothing to know in XsLT. I mean, the logic is extremely stright forward basic iterative logic and the tags used to write that logic are the same as custom tags:
Examples: <xsl:for-each /> <xsl:if /> And these are just embedded within well-formed HTML and JavaScript so really ... the only limitation I would think is if the person didn't know a little bit of xpath ... but anyone with any clue of XML knows at least a little bit of xPath. :) I hear ya about the slow XML parsers but they're getting a lot better, very fast. The ASP.NET XML parser in particular is suppose to scream. Well interesting. Its good to know that others are think along similar lines and not just me. Thanks for the thoughts (Jacob too)! Neal -----Original Message----- From: Joe Barefoot [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 04, 2002 4:36 PM To: Struts Users Mailing List 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 is slower than JSP, varying upon the complexity of the transformation. 2. Anyone working on your presentation layer must understand XSL. This eliminates web developers who know HTML/JavaScript and are savvy of custom tag usage (who *can* work on ASP/JSP pages). I actually think the idea is aesthetically pleasing, but practically not so pretty. :) peace, Joe > -----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). > > ?????? > > 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]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
