cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torsten Curdt" <>
Subject RE: something not correct with request object
Date Thu, 12 Jul 2001 13:01:18 GMT
> > Something broke my request object!
> >
> > I just upgraded to the latest CVS.
> > And I cannot get any request parameters
> > anymore. I use CA a lot.
> >
> > Carsten, maybe your last CA fixes have
> > undesired side effects? I'll have a
> > deeper look into this one...
> Yes, actually my changes for making the cocoon:// url work,
> did break this.
> The aggregated parts now do not get the original parameters
> from the request but they have one parameters, so you can
> write cocoon:/mypart?parameter=value.
> This is very important to give new and different parameters
> to the aggregated pipelines. I think this is a useful
> feature.
> For your problem there are two solutions:
> 1. You "copy" the parameters to the parts
> or
> 2. The parts get (inherit) the paramters from the original request
>    and can add their own
> Perhaps we should do the second approach?

Eeek... I don't know if I like this at all!

I need the original request object in an
action. I don't know how many parameters
there will be... IMHO copying in general
is bad idea! But how would you propose
to do the inheriting? Keep in mind that
the action has no idea if it is inside the
aggregated part or not!
Maybe as parameter for <map:part>?

    <map:part src=".." inherritRequest="true">

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

View raw message