On Monday 21 October 2002 23:29, Tod Harter wrote: > On Monday 21 October 2002 01:28 pm, Robin Berjon wrote: > > 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. > > Yeah, XML::Filter::XInclude actually works fine for me because I SAX > process my stuff as soon as I'm done with XSP, generally, and the stuff I > want to include is static anyhow. I was just wondering how come it is that > the XML parser that parses the XSP in the first place doesn't process > XINCLUDE??? Given that its going in through XML::LibXML shouldn't it kinda
I don't know what you guys are using, but I am using XInclude very happily and abundantly with XSP. It 'just works' for me. -- CU Joerg PGP Public Key at http://ich.bin.kein.hoschi.de/~trouble/public_key.asc PGP Key fingerprint = D34F 57C4 99D8 8F16 E16E 7779 CDDC 41A4 4C48 6F94 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
