Hi, this is not a very standard way of dealing with logins.
I have seen in many applications, the way you want to handle a login
is using a "Session" - not just Request.
Now, coming to your problem, I don't think request.getParameter(..)
will ever throw a NullPointerException unless the "request" itself is
not initialized. So, I guess your Null pointer Exception is not thrown
in the try{ .. } block as you showed in your code. Pleaser re-analyze
your code to see from where you are getting the Null pointer - then
you would be able to trap that situation and handle it.
HTH
> Dear All,
> My login page is index.html.
[quoted text clipped - 37 lines]
>
> Thanks in advance.
Lew - 03 Oct 2007 14:47 GMT
> Hi, this is not a very standard way of dealing with logins.
Please do not top-post.
Sameer wrote:
>> Dear All,
>> My login page is index.html.
[quoted text clipped - 35 lines]
>> Why this may be?
>> Is this the right approach? Any suggestions?
You should avoid having Java scriptlet in your JSPs. You should use
<jsp:forward> instead of redirect. Using <jsp:forward> prior to the rest of
validate.jsp means that the rest of the JSP will not render. You should keep
authentication information in the session, as send2r suggested when they also
pointed out that your NPE is never thrown.

Signature
Lew
> Dear All,
> My login page is index.html.
[quoted text clipped - 37 lines]
>
> Thanks in advance.
This is often achieved via a Servlet Filter. Add a filter, and check
for a session variable and/or a cookie that indicates a successful
auth. If no auth, redirect the user to login page, if auth'd, let him
pass. I am sure you'd find a lot of examples by Googling around on
usage of Servlet Filters to check authentication.
-cheers,
Manish