-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 21 May 2002 11:42 pm, [EMAIL PROTECTED] wrote: > matts 02/05/21 15:42:29 > > Modified: lib AxKit.pm > lib/Apache/AxKit ConfigReader.pm Provider.pm > lib/Apache/AxKit/Language LibXSLT.pm XPathScript.pm > lib/Apache/AxKit/Provider File.pm > Log: > AxKit.pm - Fix no styles + provider = provider results > Language/*.pm and Provider.pm - Changed all subrequests to "do the right > thing" - i.e. get a subrequest to use for AxKit::Cfg and get the right > provider for any subrequest. LibXSLT.pm - Assume .xsl files are style > providers and everything else is content. Lame, I know. XPathScript.pm - Do > the right thing when requesting an included stylesheet vs a document() wrt > Provider->new_XXX_provider ConfigReader.pm - better debugging of when > get_config returns undef File.pm - Support FastHandler better.
Some of you may have noticed the above rather large (and potentially dangerous?) patch. Basically it was a cascading problem - in working on an alternate provider I removed some code which punted to the File.pm provider if it couldn't parse the source. When I did that, the whole site broke, because I had a stylesheet doing document() on a plain XML file, but it was being loaded with the alternate provider because when you specify an alternate provider in AxKit it changes it for the entire request. This is obviously really quite wrong. So the above patch fixes it so that both sub-requested files via document() and included/imported stylesheets pick up the right provider, potentially at the expense of some performance. It may also fix some of the wierder relative URI bugs floating around. I'd certainly like to find out if it does. But don't hold any hopes up ;-) It also allows you to write a dynamic provider that generates XML, and use that in a document() call to have the provider actually run. I haven't tested that, but it seems like an oft-requested feature. Ironically I think it might be possible to build a Provider::AxKit to solve the "include this XSP after executing just the XSP" problem. But again, don't hold hopes up - this was really meant to fix just one bug - if it fixes/helps with any others, that's just a bonus. I have run it through my test sites, and it seems OK there, but I'm not exactly doing anything really complex most of the time. So I'd appreciate people going over it and/or testing it on their stuff. If it doesn't work for any reason I'd be perfectly willing to back some or all of it out again. I just checked it in so people could play easily. - -- <:->get a SMart net</:-> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE86tEUVBc71ct6OywRAm02AKCnLy1bf3fS8TWfQ9jZ42aZfEYJrgCdHV56 kDapczQ6A/vz3bymvmh/Tn8= =sfwi -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
