Dear colleagues,
I have built a xsp-page which takes two xml-Files and builds a xsp which
will be compiled by another pipeline:
<map:match pattern="xsp-part1">
<map:generate src="part1.xsp"/>
<map:serialize type="xml"/>
</map:match>
<map:match pattern="xsp-part2">
<map:generate src="part2.xsp"/>
<map:serialize type="xml"/>
</map:match>
<map:match pattern="xsp-main">
<map:generate src="main.xsp"/>
<map:transform type="cinclude"/>
<map:serialize type="xml"/>
</map:match>
<map:match pattern="xsp-result">
<map:generate type="serverpages" src="cocoon:/xsp-main"/>
<map:serialize type="xml"/>
</map:match>
This is not very performant, so that I tried to use the
CachingCIncludeTransformer instead of the CIncludeTransformer, but "bad"
performance did not change. My other xsp sample pages run 2-3 times faster
than this. One point is, that I have 4 pipelines here and with every new
included part I will get a further one. I think that caching of the CInclude
result will be very helpful in this case.
Is it necessary to switch the CachingCIncludeTranformer to "on"? I looked
into the source code, but I did not find anything that looks like a switch
or a helpful attribute.
Can anybody help me?
Thank you, best regards
- Volker -
---------------------------------------------------------------------
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]>
