Do you have the request module in your cocoon.xconf :)=?
Le Mercredi 04 F�vrier 2004 14:45, Derek Hohls a �crit :
> OK, so I am back to where I started ;-)
>
> i.e. I have a {request:xxx} that works fine under
> Cocoon 2.1.x, but does not work under Cocoon 2.0.x;
> i.e it just returns a blank.
>
> The log files do not report any error - what else
> could be causing this to fail?
>
> Thanks
> Derek
>
> >>> [EMAIL PROTECTED] 2004/02/04 03:41:07 PM >>>
>
> No, it means it will work :=)
>
> Le Mercredi 04 F�vrier 2004 14:35, Derek Hohls a �crit :
> > Martin
> >
> > So what does this mean? That the "RequestParameterModule"
> > mapping shown below will *not* handle the {request:} ??
> >
> > Is there another "RequestModule" that does - is this only
> > available in 2.1?
> >
> > Thanks
> > Derek
> >
> > >>> [EMAIL PROTECTED] 2004/02/04 03:22:01 PM >>>
> >
> > "Derek Hohls" <[EMAIL PROTECTED]> writes:
> > > Thanks Reinhard
> > >
> > > The cocoon.xconf on the sitemap running Cocoon 2.0.4 shows:
> > >
> > >
> > > <input-modules logger="core.modules.input">
> > > <component-instance
> >
> > class="org.apache.cocoon.components.modules.input.RequestParameterModule"
> > name="request"/>
> >
> > > <component-instance
> >
> > class="org.apache.cocoon.components.modules.input.RequestAttributeModule"
> > name="attribute"/>
> >
> > > <component-instance
> >
> > class="org.apache.cocoon.components.modules.input.RequestURIModule"
> > name="URI"/>
> >
> > > <component-instance
> >
> > class="org.apache.cocoon.components.modules.input.HeaderAttributeModule"
> > name="header"/>
> >
> > > <component-instance
> >
> > class="org.apache.cocoon.components.modules.input.SessionAttributeModule"
> > name="session"/>
> >
> > > <component-instance
> >
> > class="org.apache.cocoon.components.modules.input.StringConstantModule"
> > name="constant"/>
> >
> > > <component-instance
> >
> > class="org.apache.cocoon.components.modules.input.RandomNumberModule"
> > name="random"/>
> >
> > > <component-instance
> >
> > class="org.apache.cocoon.components.modules.input.CollectionMetaModule"
> > name="collection"/>
> >
> > > <component-instance
> >
> > class="org.apache.cocoon.components.modules.input.DigestMetaModule"
> > name="digest"/>
> >
> > > <component-instance
> >
> > class="org.apache.cocoon.components.modules.input.DateInputModule"
> > name="date"/>
> >
> > > <component-instance
> >
> > class="org.apache.cocoon.components.modules.input.NullInputModule"
> > name="nullinput"/>
> >
> > > </input-modules>
> > >
> > > I *assume* this means they are present. Nonetheless, an
> > > app which is working in Cocoon 2.1.x (on my machine) does
> > > not work on the older 2.0 version on the server.... i.e.
> > > all the {request:xxx} return null values.... ?
> >
> > The RequestParameterModule is not the same as the RequestModule.
> > IIRC {request:} was mapped to RequestParameterModule in cocoon 2.0,but
> > to
> > RequestModule in cocoon 2.1. Not sure, when exactly this changed.
> >
> > Martin
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
