It seems to me that XSP itself is an example of an application that should be written in XSLT.... IE, converting XML (XSP) to some other format (executeable perl module). At that point AxKit could work in some of the features present in things like SILLY, which can be nice.
On Friday 22 November 2002 04:48 am, Robin Berjon wrote: > Tod Harter wrote: > > I believe there is a way to tell XSLT to suppress 'extra' namespace > > nodes, > > I think that's mostly a feature of the serialisation that most processors > use. One way would be to suppress the xmlns attributes (if they are > accessible, which would depend on the engine). Another would be to simply > pass the document through a default stylesheet to get what the engine > serialises. > > >>Second, I've found that the resulting xml fragment has the xml namespace > >>written in every tag, which is rather unnecessary. > > XSP is tough to maintain. At this point it should probably be rewritten > from scratch. At some point a version of AxKit broke it in a way that made > it impossible to use with namespaced output. I wouldn't be surprised that > the fix involved declaring namespaces in a brute force fashion ;-) -- Tod G. Harter Giant Electronic Brain --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
