Probably totally irrelevant but if it stimulates thinking then maybe it will be a slight help: We had a performance problem in house once and in the course of debugging found that whenever an sql select was called, the query was run twice, once to get a count of rows and the second time to get the data.
I'm way too new to this whole arena to see how this could be applied to xsp processing but it is as close as I've got to an idea, I'm afraid.
HTH
Jon
-----Original Message-----
From: David Rosenstrauch [mailto:[EMAIL PROTECTED]]
Sent: 11 December 2001 15:37
To: [EMAIL PROTECTED]
Subject: Re: XSP page getting called TWICE! (was: Pipeline dependencies)
I posted this a couple of times here, as well as once to the Dev list. No one's written back with any suggestions so far.
I hope y'all don't mind, but I'd like to post this one more time. It's really stumping me! Please help!
==================================================
Anyone have any thoughts on this?
What could cause an XSP page to get called twice in the same request?
Tnx!
DR
At 12:07 PM 12/7/01 -0500, you wrote:
>Actually, regarding the setup below (which I mentioned in another message), I'm having a problem with it and would appreciate some help.
>
>Take a look at the sitemap segment below. And let me clarify it a bit too:
>
>The XSL stylesheet that I'm using in the transform on "pd/mergedoc.html" is generated *dynamically*, from an xsp page ("pages/gen_merge_xsl.xsp").
>
>This is working just fine, except for one small problem:
>
>For some reason, on each request, this XSP page is getting executed TWICE! Although this doesn't technically cause any errors, it's pretty inefficient since it hits the database twice, generates the xsl twice, etc.
>
>Any ideas why?
>
>Some possible thoughts I had:
>
>* perhaps the internal-only="true" is causing this?
>
>* perhaps an additional aspect of this setup is causing this: the "cocoon:/rtf_parse" generation step (not listed) is setting an "attachment" response header ("Content-Disposition: attachment; filename=myfile.rtf") so that the file will be downloaded instead of displayed directly in the browser. Could that be causing this?
>
>Any help appreciated!
>
>TIA!
>
>
>DR
>
>
>At 11:17 AM 12/7/01 -0500, you wrote:
> >It is possible. I'm using that in my site:
> >
> ><map:pipeline>
> > <map:match pattern="pd/mergedoc.html">
> > <map:generate src=""cocoon:/rtf_parse"/>
> > <map:transform src=""cocoon:/rtf_merge_data"/>
> > <map:serialize type="rtf"/>
> > </map:match>
> ></map:pipeline>
> >
> >
> ><map:pipeline internal-only="true">
> > <map:match pattern="rtf_merge_data">
> > <map:generate type="serverpages" src=""pages/gen_merge_xsl.xsp"/>
> > <map:serialize type="xml"/>
> > </map:match>
> ></map:pipeline>
> >
> >
> >DR
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet delivered
through the MessageLabs Virus Control Centre. For further information visit
http://www.star.net.uk/stats.asp
_____________________________________________________________________
Any views or personal opinions expressed within this email may not be those of Talis Information Ltd.
The content of this email message and any files that may be attached are confidential, and for the usage of the intended recipient only. If you are not the intended recipient, then please return this message to the sender and delete it. Any use of this e-mail by an unauthorised recipient is prohibited.
