Normally, Tapestry does handle this for you -- or rather, it passes
the job along to the servlet container, which will usually append a
";jsessionid=xxxx" to your requests.
However, if you're bypassing Tapestry to generate links directly --
for example, by using a plain old <a href=""> in your page, instead
of one of the link components, or a <form> instead of a <form
jwcid="@Form"> -- I doubt Tapestry will append the URL.
It would be helpful if you could send a snippet of the page template
for the form or link where the session is being lost.
Cheers,
Paul
On May 2, 2006, at 10:23 AM, Oscar Picasso wrote:
Hi,
I have a login component that creates a session scoped ASO on the
login form submission.
I works fine only if the client browser supports cookies. If not,no
session is created and obviously the ASO is lost between requests.
I thought that in case the browser not supporting cookies a SESSION
ID would be stored in the urls to keep track of the session.
Do I need to do something special to allow session creation even if
cookies are not enabled on the client side ?
Oscar
---------------------------------
Love cheap thrills? Enjoy PC-to-Phone calls to 30+ countries for
just 2¢/min with Yahoo! Messenger with Voice.
_________________________________________________________________
Piano music podcast: http://inthehands.com
Other interesting stuff: http://innig.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
