I'm not able to re-produce what you are saying so I'll probably need a more definitive test case to proceed further. Mine involved simply disabling cookies on the client side browser.
On 11/30/06, Patrick Klein <[EMAIL PROTECTED]> wrote:
Hi! I'm using last night's svn-snapshot... I recognized this problem first when i switched to tapestry 4.1 and it is persistent till now, at least for me... :| Patrick > jsessionid's should be getting encoded into the url properly. Perhaps > you aren't using the "most" up to date version of Tapestry possible. > > On 11/30/06, Patrick Klein <[EMAIL PROTECTED]> wrote: >> Hi! >> >> For some reason, url-rewriting doesn't work since i switched from >> tapestry 4.0.2 to 4.1.1 >> As in the old setup, cookies="false" is set in the Contrext-tag of the >> applications context.xml but the session-context is lost after the first >> click as the session is not encoded into the url. Adding the jsessionid >> manually to the url gets me the needed reference the the session. >> Using cookies the application works like charm but i need the ability to >> use the application more the once simultaniously on one browser. >> >> Can anyone help me out in this matter? Thanks :) >> >> Patrick >> >> --------------------------------------------------------------------- >> 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]
-- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
