Tod Harter wrote:
(actually I think the precise problem is if you XINCLUDE data during SAX processing then very strange things happen). One thing I wonder about, how come XSP doesn't support XINCLUDE? It just seems to ignore it.Well, just throw in an... XInclude taglib! Seriously, it shoudn't be hard at all. If you want it before processing, you need the streaming subset of it defined in XML::Filter::XInclude (or similar -- see under MSERGEANT); if you want it after processing (ie generate XIncludes) you need to turn the XML::LibXML option to do it on, probably by patching AxKit.
--
Robin Berjon <[EMAIL PROTECTED]>
Research Engineer, Expway
7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
