Hello, A call to my app invokes a filter which starts a session via request.getSession(true);
here is the id: czbgfo2bp5vs Then it proceeds to serve a page, but the client shows no JSESSION id. Then the client make an rpc call which again generates a new session via the filter. id: 8vl3kpun0rt5 Then the rpc call is processed in in my rpc method and gets the session id like this this.getThreadLocalRequest().getSession(); id: 8vl3kpun0rt5 I can see JSESSIONID is now set after returning from the rpc call. Subsequent calls show the filter recognize the session as id: 8vl3kpun0rt5 Is this.getThreadLocalRequest().getSession(); the only way to start a session? Why can't a filter start a session? this.getThreadLocalRequest().getSession(); will find a session created by a filter via request.getSession(true); but request.getSession(true); doesn't seem so send a cookie to the client. I really can't understand this. Help please!!!! How can I start a session in a filter and not in a rpc method? Shawn -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
