cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <>
Subject Re: [C2] request parameters automatically passed to cocoon:/process sub-pipeline
Date Wed, 23 Jan 2002 08:44:50 GMT
Carsten Ziegeler wrote:

>Stuart Roebuck wrote:
>>I notice that in the latest official release of Cocoon2, if you have two 
>>sitemap matches like:
>>>    <map:match pattern="info.html">
>>>      <map:generate src="cocoon:/info.xml" />
>>>      <map:transform src="transform.xslt" />
>>>      <map:serialize />
>>>    </map:match>
>>>    <map:match pattern="info.xml">
>>>      <map:generate type="my-request-param-generator" />
>>>      <map:serialize type="xml" />
>>>    </map:match>
>>and you request the page "info.html?param1=aparam&param2=anotherparam", 
>>the info.xml match receives the two request parameters as if it has been 
>>called with "info.xml?param1=aparam&param2=anotherparam".
>>For my current work, this is a very helpful feature, but I'm not 
>>that it is intentional, and I don't want to build reliance on a 
>>side-effect of the current implementation, particularly in light of all 
>>the good work currently going on to improve sitemap processing.
>>Could someone clarify whether this is expected behaviour.
>Yes, this is the wanted behaviour, so you can actually rely on it.
>But, you're right that this is not always wanted, we have some
>cases were we don't want to pass the parameters. I'm still thinking
>of a good way to indicate this to the procotol, for example by
>   "cocoon:/DONTPASSPARAMETERS@info.xml"
>If someone sees a good URI scheme for this, I will be very happy
>to implement that then!
Couldn't this be a different protocol, e.g. "raw-cocoon:/info.xml" ?


Sylvain Wallez
Anyware Technologies -

To unsubscribe, e-mail:
For additional commands, email:

View raw message