On Feb 10, 2005, at 12:25 AM, Jan Bauer Nielsen wrote:
We have a couple of pages at our site using a pipeline like this:
xsp -> xslt -> xsp -> xslt
That was both interesting and useful - thank you.
I've been re-designing my pipeline and have had some success, but I'm not all there yet. My initial problem was that I was using XSP to process X and then wanted to use XSP again to process Y.
I now have an Apache::Filter handler that takes care of what I was previously using XSP to process X for. I then have a custom ContentProvider that inherits from Apache::AxKit::Provider::Filter. My aim is to handle X using Apache::Filter and pass the content along to AxKit to process Y using XSP.
I don't have it working yet, because I am trying to make Y optional. I mean, X doesn't always pump out content that requires XSP processing, and I'm trying to get it to pump out <?xml-stylesheet href="NULL" type="application/x-xsp"?> (as and when required) to process X through XSP to get Y. If that doesn't work, I'm going to try AxAddRootProcessor and wrap X's content in that root tag to invoke XSP, so that it is only processed if wrapped in that root tag.
Has anyone tried anything like this?
/dave
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
