I'm playing around with AxKit, XML, and all that, and finding it very nice.
However, in writing a personal test app, I've run into a problem. I'd like to have a single XSP page that uses the ESQL to process the SQL calls, as to avoid repeating the db/password/etc info all over the place. Thus, upstream, I'd create an XML tree that has parts like: <query name="list"> <table>somesuch</table> <columns>somesuch</columns> <where>value LIKE "somesuch"</where> </query> This would then be processed by XSLT to make the right XML tree for the XSP/ESQL commands, then return back to the original XSP page's pipeline for further processing. This seems certainly reasonable, particular given the article at http://www.perl.com/pub/a/2002/07/02/axkit.html which describes a case of a XSLT upstream of an XSP page. So I've gone about making an XSP page with the following pipeline: <?xml-stylesheet href="NULL" type="application/x-xsp"?> <?xml-stylesheet href="xsl/prep_query.xsl" type="text/xsl"?> <?xml-stylesheet href="NULL" type="application/x-xsp"?> <?xml-stylesheet href="xsl/parse_list.xsl" type="text/xsl"?> <?xml-stylesheet href="xsl/page.xsl" type="text/xsl" ? Parts 1 and 2 work find. However, when I hit the second XSP processing step, things go weird. I've traced the output, and it seems that instead of using the XML output from Part 2, it restarts the XML from the original XSP file, thus making anything in the last 2 stages fail miserably. Trying inspiration, I removed the href attribute of the 3rd step, but according to debugging info, that step is invalid, and the pipeline completely skips it, making the rest of the output again useless. Any idea of how to get this working? Is there a better way to set up the pipeline? I know that I could construct the SQL back at the first XSP, but I'm trying to avoid repeating code... This is with AxKit 1.6-1 on a deb system with perl 5.8 behind it, under Apache 1.3.26-1. "Normal" pipelines, with a single XSP at the forefront, work just fine. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
