> The handling works but the problem is that after login, the
> session seems to immediately be invalid. The very first
> call made by my Applet is 'rejected' because the session
> has become invalid (i.e. the handling in the Servlet
> decides this.)
OK. What I meant was, how are you handling maintaining the session with the container? Unless you are passing the correct jsessionid cookie back to the container each time you make a request from the applet, the container won't recognise your request as belonging to an existing session.
Luke.