I did. From the trace, it seems like the whole <map:match pattern="rtf_merge_data"> pipeline is getting run twice - which I found even more confusing.
Not sure why it should need to run that pipeline twice. Clearly that's happening because of some combination of: a) it's an internal pipeline, b) I'm using the results of that pipeline in a transform in another pipeline. I can't figure out for the life of me why it should be run twice though. Thanks for giving it a shot though and please let me know if you have any other suggestions, as I still haven't solved this. DR At 08:58 AM 12/11/01 -0800, you wrote: >Have you tried modifying the code to print a stack trace with each >invocation? This might help isolate the source of each call. > >-Mitch > >-----Original Message----- >From: David Rosenstrauch [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, December 11, 2001 7:37 AM >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]> > >--------------------------------------------------------------------- >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]> --------------------------------------------------------------------- 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]>
