The biggest weakeness I see with XSLT based output is that, frankly, it
requires a very technical person to understand the nuances of XSLT.
That doesn't jive with the idea of a graphic-arts-oriented HTML
development staff working on the page designs while the development
teams works on the dynamic content.
[ [EMAIL PROTECTED] | http://DiskWise.com : free ]
[ BDE Alternatives Guide | internet-based file storage and ]
[ www.kylecordes.com | sharing, with version history ]
----- Original Message -----
From: "Andrew S Tomlinson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 12, 2000 5:46 PM
Subject: Re: Model 2 & 3 Architecture
> Mike,
> my response was to the following extract...
> <snip>
> For simple data models and simple transforms, XSLT will work just
fine.
> But if you've tried to build complex web pages using XSLT
> (for one thing, it cannot operate on multiple XML documents at the
same
> time),
> </snip>
> .. which I interpret as multiple inputs not outputs.
>
> Anyway, I do like your approach of using entities - thanks for the
tip.
> I may well come back with some questions once I've looked into this
area ;-)
>
> Regards
> @
>
>
========================================================================
===
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
> Some relevant FAQs on JSP/Servlets can be found at:
>
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
>
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
