Hi,
For the record, I would say it is very easy in XSL. This was from the original
bug report:
<map:parameter name="include" value="/manual/s1[@title='{1}']"/>
To get this with xsl you could simply:
<xsl:apply-templates
select="document($book_param)/manual/s1[@title=$section_title_param]"/>
Now, the problem might be that the book is too large... (probably not for Saxon,
though)
best,
-Rob
> -----Original Message-----
> From: Jeff Turner [mailto:[EMAIL PROTECTED]]
> Sent: Monday, September 02, 2002 4:57 PM
> To: [EMAIL PROTECTED]
> Subject: Re: DO NOT REPLY [Bug 12235] New: - [PATCH] XPathTransformer
>
>
> On Mon, Sep 02, 2002 at 07:30:21PM +0200, Joerg Heinicke wrote:
> > > While this sort of filtering can be done with XSLT, it can't be done
> > > dynamically, based on an input parameter, because XSLT template patterns
> > must
> > > be known at 'compile' time, not runtime, much like the sitemap's
> > matchers. See
> > > cocoon-users discussion:
> > > http://marc.theaimsgroup.com/?t=103069471700001&r=1&w=2
> >
> > Hmm, I think it can be done with XSLT, but you have to write XSLT by XSLT
> > or a XML file with some xinclude statements and use xinclude transformer.
>
> Given that XSLT is Turing complete [1], one can do *anything* with a
> dynamically generated XSLT ;) The issue is ease of use and efficiency,
> for which I think XPathTransformer easily beats dynamically generated
> XSLT or xinclude-including XSP pages.
>
>
> --Jeff
>
> [1] http://www.unidex.com/turing/utm.htm
>
> >
> > Joerg
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
