You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Marc Salvetti <ma...@notremanou.net> on 2005/04/10 13:59:42 UTC

Request parameters in pipeline

Hello,

I have another small issue after moving to 2.1.7 with the request-param 
module.

i first have this matcher :

        <map:match pattern="**frame_**.html">
            <map:generate src="cocoon:/body-{2}.xml"/>
            <map:transform type="omitns"/>
            <map:serialize type="html"/>
            <map:serialize type="xml"/>
        </map:match>

and then this one :

        <map:match pattern="body-boats/tt/planning.xml">
            <map:aggregate element="planning">
                <map:part src="cocoon:/planning_past/tt"/>
                <map:part src="cocoon:/planning_future/tt"/>
            </map:aggregate>
            <map:transform 
src="stylesheets/planning-setstatus2planning.xsl"/>
            <map:select type="parameter">
                <map:parameter name="parameter-selector-test" 
value="{request-param:month}{request-param:year}{request-param:nbMonth}"/>
                <map:when test="">
                    <map:transform type="planning">
                        <map:parameter name="start" value="{date:date}"/>
                        <map:parameter name="nbMonth" value="2"/>
                    </map:transform>
                </map:when>
                <map:otherwise>
                    <map:transform type="planning">
                        <map:parameter name="start" 
value="{request-param:month}/01/20{request-param:year}"/>
                        <map:parameter name="nbMonth" 
value="{request-param:nbMonth}"/>
                    </map:transform>
                </map:otherwise>
            </map:select>

          <snip/>
        </map:match>

If i access directly the url
    body-boats/tt/planning.xml?month=4&year=05&nbMonth=12 the pipeline 
works fine,
and if i access
    frame_boats/tt/planning.html?month=4&year=05&nbMonth=12
the pipeline doesn't seem to receive any of the request parameters.

This was working under 2.1.5.1

Anyone know about a change with handling the parameters or a way to 
target the problem more precisely ?

Thanks,

Marc


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org