RE: XSP page getting called TWICE! (was: Pipeline dependencies)
Hi David, yesterday I send a patch to cocoon-dev (which now was applied to 20-branch) which should solve your problem. See http://marc.theaimsgroup.com/?l=xml-cocoon-devm=100827658927876w=2 for details. Wolfram -Ursprüngliche Nachricht- Von: David Rosenstrauch [mailto:[EMAIL PROTECTED]] Gesendet am: Mittwoch, 12. Dezember 2001 17:49 An: [EMAIL PROTECTED] Betreff: RE: XSP page getting called TWICE! (was: Pipeline dependencies) Ah, but that's the rub. It's only invoked in one place in the Java code, and yet it gets called twice. Cocoon itself is calling this pipeline twice, for some reason, and I have no idea why. Thanks for the msg, though. DR At 10:04 AM 12/12/01 +0100, you wrote: David, I think what Mitch meant and I'm not sure you mean the same - you may trace down from which point of sitemap_xmap.java your pipelines are invoked. And as soon you found _two_ places of invocation in java code, you may match them back to your sitemap.xmap (you should see what exactly made your matcher to be invoked twice). Best wishes, Nick -Original Message- From: David Rosenstrauch [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 12, 2001 12:01 AM To: [EMAIL PROTECTED] Subject: RE: XSP page getting called TWICE! (was: Pipeline dependencies) 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
RE: XSP page getting called TWICE! (was: Pipeline dependencies)
Wow - sweet! Unfortunately I didn't get a quick response on the dev mailing list, and unsubscribed before I saw your post. Thanks very much for taking care of this Wolfram! DR At 11:39 AM 12/14/01 +0100, you wrote: Hi David, yesterday I send a patch to cocoon-dev (which now was applied to 20-branch) which should solve your problem. See http://marc.theaimsgroup.com/?l=xml-cocoon-devm=100827658927876w=2 for details. Wolfram -Ursprüngliche Nachricht- Von: David Rosenstrauch [mailto:[EMAIL PROTECTED]] Gesendet am: Mittwoch, 12. Dezember 2001 17:49 An: [EMAIL PROTECTED] Betreff: RE: XSP page getting called TWICE! (was: Pipeline dependencies) Ah, but that's the rub. It's only invoked in one place in the Java code, and yet it gets called twice. Cocoon itself is calling this pipeline twice, for some reason, and I have no idea why. Thanks for the msg, though. DR At 10:04 AM 12/12/01 +0100, you wrote: David, I think what Mitch meant and I'm not sure you mean the same - you may trace down from which point of sitemap_xmap.java your pipelines are invoked. And as soon you found _two_ places of invocation in java code, you may match them back to your sitemap.xmap (you should see what exactly made your matcher to be invoked twice). Best wishes, Nick -Original Message- From: David Rosenstrauch [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 12, 2001 12:01 AM To: [EMAIL PROTECTED] Subject: RE: XSP page getting called TWICE! (was: Pipeline dependencies) 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
RE: XSP page getting called TWICE! (was: Pipeline dependencies)
David, I think what Mitch meant and I'm not sure you mean the same - you may trace down from which point of sitemap_xmap.java your pipelines are invoked. And as soon you found _two_ places of invocation in java code, you may match them back to your sitemap.xmap (you should see what exactly made your matcher to be invoked twice). Best wishes, Nick -Original Message- From: David Rosenstrauch [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 12, 2001 12:01 AM To: [EMAIL PROTECTED] Subject: RE: XSP page getting called TWICE! (was: Pipeline dependencies) 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] - 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
RE: XSP page getting called TWICE! (was: Pipeline dependencies)
Ah, but that's the rub. It's only invoked in one place in the Java code, and yet it gets called twice. Cocoon itself is calling this pipeline twice, for some reason, and I have no idea why. Thanks for the msg, though. DR At 10:04 AM 12/12/01 +0100, you wrote: David, I think what Mitch meant and I'm not sure you mean the same - you may trace down from which point of sitemap_xmap.java your pipelines are invoked. And as soon you found _two_ places of invocation in java code, you may match them back to your sitemap.xmap (you should see what exactly made your matcher to be invoked twice). Best wishes, Nick -Original Message- From: David Rosenstrauch [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 12, 2001 12:01 AM To: [EMAIL PROTECTED] Subject: RE: XSP page getting called TWICE! (was: Pipeline dependencies) 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
RE: XSP page getting called TWICE! (was: Pipeline dependencies)
Title: RE: XSP page getting called TWICE! (was: Pipeline dependencies) 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.
RE: XSP page getting called TWICE! (was: Pipeline dependencies)
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]
RE: XSP page getting called TWICE! (was: Pipeline dependencies)
Thanks for the suggestion. Not sure that's the problem though. Seems like the whole map:match pattern=rtf_merge_data pipeline is getting run twice. 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 04:11 PM 12/11/01 +, you wrote: 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]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.htmlhttp://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.asphttp://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.asphttp://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. - 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
RE: XSP page getting called TWICE! (was: Pipeline dependencies)
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]
Re: XSP page getting called TWICE! (was: Pipeline dependencies)
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]
XSP page getting called TWICE! (was: Pipeline dependencies)
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]
Re: XSP page getting called TWICE! (was: Pipeline dependencies)
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]
