Turn your question around....... Think about all the developers out there that DONT use CFMX. By using XML and XSLT you can avoid THEM having to introduce another technology into their equation (i.e. Cold Fusion).
But all the other comments about the "why's" still apply as well. Like Sean says, the syntax of XLST can be an absolute pain - but not for those familiar with it. I would say, if you want to deploy a system that allows people with XML/XSLT experience to tailor your system - then that would be a perfect reason to use it in preference to walking the XML nodes yourself in CFMX. Another more "generic" reason to use it would be to completely separate the presentation and data layers. On the other hand, if you are proficient in traversing the XML DOM in CFMX - and don't need (or want) to learn XLST - then go with the CFMX/XML approach. That is what we have done here. However, having said all of that, there is benefit in learning at least the basics of XSLT - even if only for using add-on's like FOP (a JAR for create PDF's from things like CFMX). Does any of that help ? Regards, Gary --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
