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]>
