Sorry, I was wrong. In my case the problem was that "redirectTo" url was created before session. And thus before putting jsessionid in url. So the login was working fine - it was appending "jsessionid" to the url and then my code was redirecting to the old "redirectTo" url without "jsessionid".
On Mon, Jul 27, 2009 at 9:52 AM, Sergey Didenko <sergey.dide...@gmail.com>wrote: > I have the same bug. > > I tried to catch it. > > It seems that ApplicationStateManager does not trigger url based session > tracking when setting a session object from a service. But it works ok if > there a "write" to session from a component. > > I will create a JIRA if there is no objections. > > Regards, Sergey. >
