David Nolan wrote:As others have pointed out, writing an AxKit provider to fetch the XML from your ColdFusion server should be possible. But I'm not sure why you would want to do that, since ColdFusion MX supports XSL transformations natively. Maybe thats a newer version of ColdFusion then you're using...
It seemed from the original post that that's what he was doing. There may be reasons for going another route though. Maybe CF doesn't cache XSLT operations. Maybe he wants some post-processing with AxKit beyond just XSLT. Maybe he's transitioning out of tools sold by the Evil Empire progressively...
Yes on all accounts. I am using an older version of CF and the the XSLT operations arent the quickest thing and I would love the ability to mix in some PHP or whatever and just let AxKit/Apache transform it out.
>The provider approach would involve writing a small perl module that provides certain methods that would be used by AxKit to fetch the XML, instead of fetching it from a file on the disk. See this page for documentation: http://www.axkit.org/wiki/view/AxKit/ProviderHowTo
It should be truly trivial. The provider's get_strref() would call get() from LWP::Simple (or something slightly more elaborate if POST is needed -- but that won't be hard either).
My major concern with this approach is that it be entirely transparent. So I would want my URL's to still look like: myserver.com/page.cfm and then AxKit would step in and take the output and transform it, but only if it was actually XML output, since I dont want to have to be forced to only generate XML output.
The reason I was asking about apache 2 is that I'm wondering if all this will be much easier when AxKit does support apache 2?
Thanks, /brian
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
