On Feb 3, 2005, at 6:02 PM, Matt Sergeant wrote:
On 3 Feb 2005, at 14:16, Dave Roe wrote:
I've been looking at how AxKit::XSP::Wiki works. Is it not the case that there are two different XSP passes here?
The way I see it, "view" and "edit" are XSP pages (the first XSP pass) that output <xspwiki /> content. AxAddRootProcessor application/x-xsp NULL xspwiki means that this output is again run through XSP, so that <wiki:display-page /> is handled by the taglib (the second XSP pass).
Does AxKit::XSP::Wiki work like this? Does it suffer from your above description?
It doesn't work like you say. It has a single XSP pass.
Thank you for clarifying that. I've looked at it further and written a testcase or two to try to better understand it. Is it correct to say that any XML output as <xsp:content /> is also run through the XSP engine before final output? Otherwise, how would view/edit output XML containing <wiki:display-page /> which invokes the tag library that creates the XSP output?
Regardless, this does not allow taglib A to output <taglibB:tags /> destined to be processed by XSP. They simply move onto the next step in the pipeline, in my case XSL, unprocessed. Is there a way of chaining taglibs together that I should keep looking for, or should I be re-thinking the problem?
And congratulations on what I trust was (otherwise) a successful emigration experience.
Thanks, /dave
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
