wicket session is not persisted in httpsession until you hit a > stateful page. to manually persist the wicket session call .bind() on > it. >
Hmmm... Although that is very useful information to know, that did not work. :-( So, let me ask this another way... How does Wicket associate a given request to a Session? The incoming request that I need to associate to the user's session is from a different location (OpenId Provider). So, even when I create a persistent session with bind(), Wicket has no way of knowing that the new request is part of that Session. So, how can I tell Wicket that this incoming request is part of that Session? Thanks! =David.Leangen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
