To utilize a bean is quite easy (without even changing your current solution dramatically). You would just create a java class that has a public default constructor and has a public getx and a public setx method for each class attribute x. For example:
public class SessionBean
{
String userName = "";
public SessionBean() {}
public String getUserName () { return userName; }
public void setUserName (String _name) { userName = _name; }
}
There's a bean class, then if you just use the usebean tag as I described and the setproperty and getproperty tags (there's plenty of free jsp references online for these tags) you can utilize your current solution and just incorporate a very simple bean for 'carrying' the relevant data between pages. Also, another handy point: If a form is submitted to a jsp page with this bean the following tags will set all class attributes which have the same name as input fields in the form...In this case userName would be given the value of a textbox whose name is userName also if the form's action was set to a jsp page with the following tags:
<jsp:useBean id="SessionBeanId" scope="session" class="SessionBean" />
<jsp:setProperty name="SessionBeanId" property="*" />
Hope this clarifies some of the bean things....
-MLA
PS If you really do not want to use beans, then you could always stick with hidden input fields which repetitively hold the value of the main form's fields (in other words every form has hidden input fields which inherit the values from the previous form or is updated by javascript or something).