Vadim,
> Back to basics... You can either ask user list on how to do this or
> simply use:
>
> <map:match pattern="path/cacheable">
> ... pipeline goes here ...
> </map:match>
I am sorry to be so stupid here but I don't understand! :-(. I know I
can use a general pattern in the match pattern, but how does that help
me when I create the src attribute for map:part, which somehow needs to
know about the query string? Suppose I have:
<map:match pattern="path/cacheable">
<map:aggregate element="root">
<map:part src="cocoon://path/cacheable">
</map:aggregate>
<map:serialize/>
</map:match>
<map:match pattern="cacheable">
<map:generate type="serverpages" src="cacheable.xsp"/>
<map:serialize/>
</map:match>
This will work--but since map:part's src doesn't contain the query
string, there will only be one key generated, which will prevent results
generated from different query string results from being cached. You
say I need to aggregate using:
>> cocoon://path/cacheable?param=some-value
If we are using page-number, then it looks like:
<map:match pattern="path/cacheable">
<map:aggregate element="root">
<map:part src="cocoon://path/cacheable?page-number=WHATGOESHERE?">
</map:aggregate>
<map:serialize/>
</map:match>
Thank you for your help....
--Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
