Thanks Andy, That's very strange. I've tested this scenario (with cookies enabled and disabled) with a RequestFilter with http redirect as a re-entry point.
In the service method when I'm calling: TAState state = stateManager.getIfExists(TAState.class); this allways retrun null no matter what. Also I've tested with a page as a re-entry: @ApplicationState private TAState state; this is also null. Very weird! Some parameters (like jsessionid) can be provided as needed if user don't have cookies enabled. Cheers! On Fri, Nov 28, 2008 at 6:01 PM, Andy Pahne <[EMAIL PROTECTED]>wrote: > > The session reattachment part: as long as the session id is stored in the > default place (cookie), it should work right out of the box. It does not > matter if the browsing session is interrupted shortly, as long as the > session does not time out or the user closes and reopens his browser. > > I don't understand the parameters thing. Please be a bit more specific. > > Andy > > > > > > Ovidiu Hurducas schrieb: > > Hi! >> I have a Tap 5 (5.0.15) application with the following scenario: >> >> User access a page and init ASO -> User than leave on a 3'rd party site >> (can >> save some params here) -> user come back on my site and wants to access >> the >> ASO again (saved params can be provided here) >> >> So the questions are: How do I reattach the user to its previous session? >> What parameters should be provided in order to achieve that? >> What is the best option for re-entry point? (page, RequestFilter, anything >> else?) >> >> Thank you! >> >> --Ovidiu >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
