>> Sounds like you may want to store j_username in session scope
>> (session.setAttribute() ), rather than request scope, since you are
[quoted text clipped - 4 lines]
> I would like to do that, but I can't. The entire process is handled by
> the server. To log the use in I don't use my code
It seems like a lot of bother, but you could probably set up a servlet
filter that captured the provided j_username and stashed it in the
session. If the login form is provided via JSP then it could easily
retrieve the value from the session and use it to set the initial value
of the username field when the form is displayed again.
I'd have to study the docs to decide, but it might work to stash the
data in the request rather than in the session; this would be better if
it works.
Overall, the form login system seems to provide relatively little
information back to the web application. To me, this is one of its more
egregious weaknesses.

Signature
John Bollinger
jobollin@indiana.edu
Andrea Desole - 20 Jan 2006 09:15 GMT
> It seems like a lot of bother, but you could probably set up a servlet
> filter that captured the provided j_username and stashed it in the
[quoted text clipped - 5 lines]
> data in the request rather than in the session; this would be better if
> it works.
I have the feeling that filters are not called with form based login,
since it is completely handled by the server, and it does seem like a
lot of bother, but I'll think about giving it a try. If I want to do it
this is so far the only possible solution I have. Thanks
> Overall, the form login system seems to provide relatively little
> information back to the web application. To me, this is one of its more
> egregious weaknesses.
I agree. Actually it looks like it hasn't been designed to be very
powerful. But unfortunately this is a requirement I have