We are finding Jaxen and Dom4j a quite effective match with XPath. We are using it for handling tree menus with having an action just pass back xml where the JSP checks the request header to see if the transformation can be done client side, else we pass it through JSTL tags server side. We will probably end up doing the same for other pages.
Even our Realm (Security) implementation uses all XML and XPath to handle complex role management. XML Rox! -Jacob | -----Original Message----- | From: neal [mailto:[EMAIL PROTECTED]] | Sent: Wednesday, September 04, 2002 6: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:struts-user- | [EMAIL PROTECTED]> | For additional commands, e-mail: <mailto:struts-user- | [EMAIL PROTECTED]> | | --- | Incoming mail is certified Virus Free. | Checked by AVG anti-virus system (http://www.grisoft.com). | Version: 6.0.381 / Virus Database: 214 - Release Date: 8/2/2002 | --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.381 / Virus Database: 214 - Release Date: 8/2/2002 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
