Return-Path: 
 <users-return-62373-apmail-cocoon-users-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-users-archive@www.apache.org
Received: (qmail 14016 invoked from network); 4 Feb 2004 14:27:03 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 4 Feb 2004 14:27:03 -0000
Received: (qmail 7996 invoked by uid 500); 4 Feb 2004 14:26:27 -0000
Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org
Received: (qmail 7979 invoked by uid 500); 4 Feb 2004 14:26:26 -0000
Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:users-help@cocoon.apache.org>
list-unsubscribe: <mailto:users-unsubscribe@cocoon.apache.org>
list-post: <mailto:users@cocoon.apache.org>
Reply-To: users@cocoon.apache.org
Delivered-To: mailing list users@cocoon.apache.org
Received: (qmail 7721 invoked from network); 4 Feb 2004 14:26:24 -0000
Received: from unknown (HELO wabe.csir.co.za) (146.64.10.166)
  by daedalus.apache.org with SMTP; 4 Feb 2004 14:26:24 -0000
Received: from cs-emo.csir.co.za (cs-emo.csir.co.za [146.64.10.40])
	by wabe.csir.co.za (8.12.5/8.12.5) with ESMTP id i14EQ8ET007292
	for <users@cocoon.apache.org>; Wed, 4 Feb 2004 16:26:08 +0200
Received: from GW-EMO-MTA by cs-emo.csir.co.za
	with Novell_GroupWise; Wed, 04 Feb 2004 16:26:07 +0200
Message-Id: <s0211d1f.067@cs-emo.csir.co.za>
X-Mailer: Novell GroupWise Internet Agent 6.5.1 
Date: Wed, 04 Feb 2004 16:25:40 +0200
From: "Derek Hohls" <DHohls@csir.co.za>
To: <users@cocoon.apache.org>
Subject: Re: obtaining Servername and Port in Sitemap
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-MailScanner-Information: Please contact sys-admin at csir.co.za for more
 information
X-MailScanner: Found to be clean
X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-4.9, required 8,
	BAYES_00 -4.90)
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Ok - now I am lost.   I guess its going to be
simpler to get  the server version upgraded
otherwise this type of thing will no doubt continue
to happen!

>>> ntoper@jouve.fr 2004/02/04 04:14:42 PM >>>
Try it with the session transformer. Otherwise you might have to add in you=
r=20
cocoon.xconf the input module and of course the class files
Le Mercredi 04 F=E9vrier 2004 15:09, Derek Hohls a =E9crit :
> The only request modules I have are the ones
> shown below - if it is supposed to be here, but
> isn't, where and how do I obtain it so that it is
> present?
>
> Thanks
> Derek
>
> [Sorry, do not do understand your 'smilie'??]
>
> >>> ntoper@jouve.fr 2004/02/04 03:58:33 PM >>>
>
> Do you have the request module in your cocoon.xconf :)=3D?
>
> Le Mercredi 04 F=E9vrier 2004 14:45, Derek Hohls a =E9crit :
> > 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
> >
> > >>> ntoper@jouve.fr 2004/02/04 03:41:07 PM >>>
> >
> > No, it means it will work :=3D)
> >
> > Le Mercredi 04 F=E9vrier 2004 14:35, Derek Hohls a =E9crit :
> > > 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
> > >
> > > >>> holz@fiz-chemie.de 2004/02/04 03:22:01 PM >>>
> > >
> > > "Derek Hohls" <DHohls@csir.co.za> writes:
> > > > Thanks Reinhard
> > > >
> > > > The cocoon.xconf on the sitemap running Cocoon 2.0.4 shows:
> > > >
> > > >
> > > >    <input-modules logger=3D"core.modules.input">
> > > >       <component-instance
> > >
> > > class=3D"org.apache.cocoon.components.modules.input.RequestParameterM=
odul
> > >e" name=3D"request"/>
> > >
> > > >       <component-instance
> > >
> > > class=3D"org.apache.cocoon.components.modules.input.RequestAttributeM=
odul
> > >e" name=3D"attribute"/>
> > >
> > > >       <component-instance
> > >
> > > class=3D"org.apache.cocoon.components.modules.input.RequestURIModule"
> > > name=3D"URI"/>
> > >
> > > >       <component-instance
> > >
> > > class=3D"org.apache.cocoon.components.modules.input.HeaderAttributeMo=
dule
> > >" name=3D"header"/>
> > >
> > > >       <component-instance
> > >
> > > class=3D"org.apache.cocoon.components.modules.input.SessionAttributeM=
odul
> > >e" name=3D"session"/>
> > >
> > > >       <component-instance
> > >
> > > class=3D"org.apache.cocoon.components.modules.input.StringConstantMod=
ule"
> > > name=3D"constant"/>
> > >
> > > >       <component-instance
> > >
> > > class=3D"org.apache.cocoon.components.modules.input.RandomNumberModul=
e"
> > > name=3D"random"/>
> > >
> > > >       <component-instance
> > >
> > > class=3D"org.apache.cocoon.components.modules.input.CollectionMetaMod=
ule"
> > > name=3D"collection"/>
> > >
> > > >       <component-instance
> > >
> > > class=3D"org.apache.cocoon.components.modules.input.DigestMetaModule"
> > > name=3D"digest"/>
> > >
> > > >       <component-instance
> > >
> > > class=3D"org.apache.cocoon.components.modules.input.DateInputModule"
> > > name=3D"date"/>
> > >
> > > >       <component-instance
> > >
> > > class=3D"org.apache.cocoon.components.modules.input.NullInputModule"
> > > name=3D"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: users-unsubscribe@cocoon.apache.org=20
> > > For additional commands, e-mail: users-help@cocoon.apache.org=20
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org=20
> > For additional commands, e-mail: users-help@cocoon.apache.org=20
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org=20
> For additional commands, e-mail: users-help@cocoon.apache.org=20


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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.


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