This is what i did, thanks a lot Dirk.
I put this param in the login page as hidden field, so i can put it
again in the session during authentication. 

Regards,

Phil



On Wed, 2004-07-28 at 04:37, Dirk Gronert wrote:
> Philippe Guillard wrote:
> > Thanks Dirk,
> > 
> > Unfortunately i think global parameter is more a constant, i mean i
> > didn't find a way to change its value dynamically. Right?
> 
> 
> > 
> > Regards,
> > 
> > Phil
> > 
> > 
> > On Mon, 2004-07-26 at 22:01, Dirk Gronert wrote:
> > 
> >>Philippe Guillard wrote:
> >>
> >>>Hi all,
> >>>
> >>>I need to pass a paramter from URI to the portal and somehow access it
> >>>from my coplets.
> >>>More clearly URI could be : samples/blocks/portal/portal?my_param="foo"
> >>>or : samples/blocks/portal/foo
> >>>
> >>>I tried this : 
> >>>
> >>><map:match pattern="portal">     
> >>> <map:act type="session-propagator">
> >>>      <map:parameter name="my_param" value="{request-param:my_param}"/>
> >>></map:act>         
> >>>
> >>>works fine for the anonymous page coplets, but as soon as the user logs
> >>>in, a new session object is created and my paramter is lost.
> 
> because as an anonymous user you are logged in as an anonymous that 
> means you have a session-object! if you try to login with a other name 
> the old session of the anonymous-user is terminated (with all contexts) 
> and a new will be created. So you have to store the parameter in the 
> session after the login is procceed! that is possible becaus the request 
> object is in all components available! !!!
> 
> I hope that hepls you!
> 
> Dirk
> >>>
> >>>I tried also to use a global sitemap parameter, but don't know how to
> >>>pass it to mounted subsitemaps where my coplets are...
> >>
> >>if you set the global sitemap parameter in the rootsitemap you can use 
> >>it in alle subsitemaps. e.g.: {global:name}, so you donn't have to pass it!
> >>
> >>Dirk
> >>
> >>>Any idea ?
> >>>
> >>>Regards,
> >>>
> >>>Phil
> >>
> >>
> >>---------------------------------------------------------------------
> >>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]

Reply via email to