On Friday, April 11, 2003, at 02:53 PM, Chris Leishman wrote: <snip>
I guess my way of doing it would be XML -> XSLT (which creates XHTML but also includes XSP tags) -> XSP -> XHTML.
That way the XSLT is still responsible for creating the XHTML and then the XSP just adds in the dynamic elements. But I could see situations where you might want to use some intermediate XML format and then do a final XSLT to create XHTML.
Actually - the Cocoon guys have covered this topic in their basic concepts introduction:
http://xml.apache.org/cocoon/userdocs/concepts/index.html#c2- abstractions
Their conclusion is pretty much the same as mine - starting with XSP in the pipeline is ok for examples but bad for real systems. Better to use a 'logicsheet' (xslt) to create an xsp page to be processed. And as soon as people start trying to do this, incremental caching is invaluable...
Regards, Chris
PGP.sig
Description: This is a digitally signed message part
