The final decision, how to encode your url is still up to your servlet-container. After all, it manages sessions and decides whether to use cookies or encoded url's. So, make sure that 1. url-encoded sessions are enabled for your browser (config-setting) 2. your browser's cookie support is turned off. 3. you Tapestry service does something that creates a user-session. Tapestry itself does only create user session if it's really necessary (i.e. persistent page properties, Visit-Object created)
hth Marcus > -----Original Message----- > From: Leo Sakhvoruk [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 03, 2005 6:03 AM > To: Tapestry users > Subject: URL session encoding mystery... > > > Hello everyone, > > I'm using Tapestry 3.0.3 and trying to implement a custom > service, but > having a crazy time with getting session id encoded into the > URL string. > Is there some magic that Tapestry does behind the scenes that > determines > whether the session is persisted via cookies instead of the > URL even if > you tell it to create statefull URL's (via a boolean parameter when > calling 'constructLink')?! I've traced the code all the way to the > EngineServiceLink constructURL method and still it seems that > '_cycle.encodeURL' doesn't return a URL with a session id? Am > I just crazy? > > Please, please help! > > Leo > > --------------------------------------------------------------------- > 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]
