Assuming we could have a sub-pipeline, what would be the
best/preferred/proper way to kick it off:
Add different/new processing instructions into the base doxument, or
<?xml-stylesheet pipeline="foo1" ...?>
<?xml-stylesheet pipeline="foo2" ...?>
<?xml-stylesheet pipeline="foo2" ...?>
<?xml-stylesheet pipeline="foo1" ...?>
Use a TagLib in the initial pipeline doc that in turn fired off a new
pipeline?
<foo:pipeline process />
-=Chris
> -----Original Message-----
> From: Steve Willer [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 25, 2002 3:58 PM
> To: Matt Sergeant
> Cc: Chris Wenham; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Using the AxKit Pipeline in other ways
>
>
>
> On Thu, 25 Apr 2002, Steve Willer wrote:
>
> > On Thu, 25 Apr 2002, Matt Sergeant wrote:
> >
> > > Steve Willer and Jorg were both at one time working on
> being able to call
> > > AxKit from within AxKit (as a subrequest). Should be
> quite possible, but
> > > probably needs some issues fixed. Then you'd be able to
> request something
> > > like "axkit://order.xsp".
> >
> > It's working for me, but...well, I sorta had to dump the
> AxKit part and
> > just keep XSP and TLH.
> >
> > It also was definitely not easy, because there's typically
> a lot of code
> > that calls mod_perl (to do redirects, to "exit", to get and set
> > parameters, to retrieve posts, to set content-type, etc.).
>
> Oh...sorry, I was responding to what I thought you were saying. I was
> trying to solve two major problems:
>
> a) can't run XSP/XSL pipelines outside Apache
> b) can't execute XSP files in a subrequest (e.g. bring in
> dynamic content
> through an XSL document() call)
>
> I was talking about (a), you were talking about (b). I solved both by
> getting out of AxKit, sadly. I think (b) would be fairly easy to do,
> however. We would begin by removing the "if I'm in a subrequest, don't
> process" code in AxKit.pm. We'd also need to have the system
> keep track of
> whether it's an inner or outer instantiation of AxKit, and
> have a special
> rule in the pipeline definition that says "quit at this point if I'm a
> subrequest".
>
> I'll expand on that last step by describing an example pipeline:
>
> FOR foo.xml:
> - process it as XSP if it's XSP
> * quit here if we're in a subrequest
> - run it through foo.xsl
> - run it through layout.xsl
>
> That * rule would have to be added.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
