Having browsed the list archive, I can see that people have been interested in dynamic pipelines as such, but the most dynamic I have seen is the HowTo that uses "if" attributes to conditionally processing existing documents. The code for Provider::CGI/DOM/OpenOffice doesn't do much WRT get_styles(), although the AxKit::Provider docs are clear on what it should return:
<?xml-stylesheet type="text/xsl" href="/tests/test1.xsl"?>
produces:
$VAR1 = 'styles'; $VAR2 = [ { 'media' => 'screen', 'href' => '/tests/test1.xsl', 'title' => '#default', 'type' => 'text/xsl', 'alternate' => 'no', 'module' => 'Apache::AxKit::Language::LibXSLT' } ];
It seems to me that what I want to be able to do is handle the call to get_styles(), returning one or more entries like the above except href => 'file_on_disk' would be replaced with, ideally, the XML::LibXML::Document I have created that contains the dynamic XSL. Is there an alternative to href that will do that, or perhaps an axkit: URI?
AxKit::Cache looks interesting, in that I might be able to place my dynamic XSL in the cache in the hope that it will be picked up during get_styles(). Is this approach feasible?
On a side note, can anyone confirm the following: taglibs work with XSP, and once you enter the XSL pipeline stage, taglib elements will not behave as you might expect. Or more specifically, using taglib elements in XSL effectively re-introduces XSP into the pipeline, therefore causing the XSP to be re-compiled before being used. Simply put, should I think of taglib elements as something to be used in XSP and not XSL?
Regards, /dave
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]