public String profile;
public String password;
public Logon (String profile, password) {
this.profile = profile;
this.password = password;
}
}
Stuff that instance into the session object:
String profile = request.getParameter("profile");
String password = request.getParameter("password");
Logon log = new Logon(profile, password);
session.setAtrribute("logon", log);
%>
The Logon.jsp redirects to your home page.
Every page that requires logon info will have the following code:
Logon log = (Logon)session.getAttribute("logon");
if (log == null) {
%>
<% } %>
If the Logon object is successfully retrieved from the session context, your JSP will have access to the profile and password:
<%
String profile = log.profile;
String password = log.password;
%>
And your JDBC calls or whatever can use it.
For a more robust Logon example, look at the example application that comes with Jakarta's Struts.
--Don Denoncourt


Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online