-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Scott Penrose schrieb: | | On 27/06/2005, at 16:39, Tom Schindl wrote: | |> -----BEGIN PGP SIGNED MESSAGE----- |> Hash: SHA1 |> |> Hi Marc, |> |> (I'm also cc'ing the dev list that more people can get help from your |> question and hopefully my answer) |> |> no TomKit is not an PerlResponseHandler it works in 2 Phases: |> a) Fixup |> (b) PerlResponse) |> c) OutputFilter |> |> An example configuration can be found at: t/conf/extra.conf.in but it |> looks something like this: |> |> - -----------------------8<----------------------- |> <Location /xslt/base.xml> |> ~ PerlFixupHandler Apache2::TomKit |> ~ PerlSetVar AxAddProcessorDef "text/xsl=>xslt/base.xsl" |> ~ PerlSetVar AxAddProcessorMap |> "text/xsl=>Apache2::TomKit::Processor::LibXSLT" |> </Location> | | | This example: | | PerlFixupHandler Apache2::TomKit | PerlSetVar AxAddProcessorDef "text/xsl=>test.xsl" | PerlSetVar AxAddProcessorMap "text/ | xsl=>Apache2::TomKit::Processor::LibXSLT" | AddType application/x-httpd-php .php .phtml .php3 | AddType application/x-httpd-php-source .phps | | Will execute a PHP example and then put it through TomKit XSL | processing (which I am sure can be done otherways, but for me the | integration of the perl and php is key). | | Interesting note though that the above AxAddProcessorDef does not work | for me, it always fails to process with that XSL, however adding: | | echo "<?xml-stylesheet type=\"text/xsl\" href=\"test.xsl\"?>\n";
Well it seems that there's a bug in my implementation then. I'll look at it closer can you please file a bug with an example. It must have something to do how I deal with resources that are not handled by the default-handler but instead another one. [...] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCv7ffkVPeOFLgZFIRAm9mAJoDfC9CiOc3aoGzaDnUQwW02Io4CACfQyi5 3MAaVbydoDM0h3WffF8vTQo= =pK/h -----END PGP SIGNATURE-----
