If I'm reading you right then I will probably have to use http calls then. Perhaps it will benefit if I explain more what I am doing.
I've designed an XSP doc that, via ESQL, queries a database for a particular user and returns various statistics. I've designed this page so that the user queried is read via the xsp param tags so that one xsp page can be used to query multiple users. My larger XSP page will have an array and re-run the user.xsp page for each user and then insert some other misc. info BETWEEN each result. I've gotten this to work with http calls but not via a direct file include because I cannot pass the user to be queried. If I rewrite the user.xsp to loop through an array then I wouldn't get the misc. stuff I'm shoving between each result...and if I rewrite the user.xsp to include this misc stuff then I lose the modularity of user.xsp...which was written specifically to be useable in multiple pages...so is http requests the only way to go at this point? Cliff -----Original Message----- From: J�rg Walter [mailto:[EMAIL PROTECTED]] Sent: Monday, May 06, 2002 10:17 PM To: [EMAIL PROTECTED] Subject: Re: Layering XSP's On Monday, 06. May 2002 21:57, Cliff Galiher wrote: > I can try this: > <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; > href="/htdocs/something.xsp?user=cgaliher"/> > > The xsp page doesn't see the params passed which I guess is to be expected. [...] > So my question is: Is there a way to pass paramters to a file URI similar > to example 1 so I don't have to suffer the consequences I would if I used > example 2? No, hot the way you do it, because via xinclude, the XML is assembled as it is being read, it is not processed separately. When you are using the http URL, the resulting XML would be processed once more in the calling XSP page, which you probably don't want. But there is a way out: Design your included XML in a way that it runs as if it were a fragment of a larger XSP page (so, for example, no XSP tags that are already in the main document, like <xsp:page> etc.). The easiest way to do this is to write one XSP page without xinclude and then cut&paste the reusable part out of it, put it inside a dummy root tag and include it. For passing values to and from the included part, you can use plain perl variables. Maybe that isn't even neccessary since the included part has access to $r and everything else the main XSP page has. With xinclude, it is processed as one large XML document, AxKit never notices that it came from two files. -- CU Joerg PGP Public Key at http://ich.bin.kein.hoschi.de/~trouble/public_key.asc PGP Key fingerprint = D34F 57C4 99D8 8F16 E16E 7779 CDDC 41A4 4C48 6F94 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
