An aggregation part calls another pipeline, this pipeline can also be
accessed from an external client and these cannot pass sitemap parameters.
If however you do need to pass (yess Jorg, it does work!) a parameter, u
need to build the URI to call the pipeline with request-parameters as
index.html?param=value
I do have another strange setup with sitemap parameters (here the origin of
the former problem really lays ):
I use an authentication and then call a resource within that pipeline, it
would be easy to have the 'role' sitemap parameter (available after the
authentication action) in the resource, and then further down the line. I
can pass the parameter simply to the resource, but then because of the
former issue, will have to pass it further as a request parameter.(still
following??)
<map:match pattern="**.html">
<map:act type="auth-protect">
<map:parameter name="handler" value="VbAuthenticationHandler"/>
<map:call resource="AggregatedPage">
<map:parameter name="role" value="{role}"/>
</map:call>
</map:act>
</map:match>
This does pass it to the resource, and then I'll have to use it as <map:part
src="index.html?role={role}"/>
Well this is my first guess, if it does not work, you'll notice!:-)
Greetings,
Jan
----- Original Message -----
From: "Nicolas Toper" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 21, 2004 11:14 AM
Subject: Re: [map:aggregate] passing sitemap parameter
> Well, why can't we pass parameter to a map:part. I think it should be
> possible. Is there a reason why it is not the case? (like break Soc,...)
>
> Le Mercredi 21 Janvier 2004 11:10, Jan Hoskens a �crit :
> > Hmm, that wasn't to smart of me, I was treating the <map:part> more or
less
> > like a generator/transformer, but it only calls the pipeline. Thanks for
> > reminding me, David!
> >
> > Greetings,
> >
> > Jan
> >
> > ----- Original Message -----
> > From: Carmona Perez, David
> > To: [EMAIL PROTECTED]
> > Sent: Wednesday, January 21, 2004 10:54 AM
> > Subject: RE: [map:aggregate] passing sitemap parameter
> >
> >
> > You must set a parameter to a value, thorugh an action or a matcher.
> >
> > In this case, who sets the 'test' parameter?
> >
> >
> >
> >
> > --------
> >
> > David
> >
> >
> >
> > -----Mensaje original-----
> > De: Jan Hoskens [mailto:[EMAIL PROTECTED]
> > Enviado el: mi�rcoles, 21 de enero de 2004 10:48
> > Para: [EMAIL PROTECTED]
> > Asunto: [map:aggregate] passing sitemap parameter
> >
> >
> >
> > Hi,
> >
> >
> >
> > I tried to pass a parameter within my aggregation:
> >
> >
> >
> > ...
> >
> > <map:aggregate element="Document">
> > <map:part src="cocoon:/index" strip-root="true">
> > <map:parameter name="test" value="testval"/>
> > </map:part>
> > </map:aggregate>
> >
> > ...
> >
> >
> >
> > <map:match pattern="index">
> > <map:generate type="serverpages" src="pages/index.xsp">
> > <map:parameter name="test" value="{test}"/>
> > </map:generate>
> > <map:serialize type="xml"/>
> > </map:match>
> >
> >
> >
> > When I show the parameter test, it always is empty. I looked at the
logs,
> > but when the part is called, I don't see where the parameter gets
passed:
> >
> >
> >
> > sitemap.log:
> >
> > Current Sitemap Parameters:
> > LEVEL 1
> > PARAM: '0' VALUE: 'index'
> >
> >
> >
> > that's all!
> >
> >
> >
> > Why can't I pass parameters to a part? Or am I doing something wrong?
> >
> >
> >
> > setup: cocoon cvs head 2.1, updated yesterday
> >
> >
> >
> >
> >
> > Greetings,
> >
> >
> >
> > Jan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
