This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
You are not doing anything to set the value of your input elements. If you want to preload an element with a value it needs a value attribute.
In your example, something like:
Disclaimer: not that I would do things this way. I would never submit to a JSP -- always to a servlet, and I would favor the JSTL over scriptlet expressions. But that's another show... [ May 11, 2005: Message edited by: Bear Bibeault ]
In (at least what I would consider) a properly achitected web application, JSPs serve as presentation mechansims only. They perform no processing of their own except what is necessary for "display support". Such a pattern is frequently refered to as "Model 2" or "MVC" or even "n-tiered". There has been much written on these subjects.
Inherently, when submitting a form, processing of the form data occurs. Such processing is inappropriate for a JSP in a web app following this pattern.
In fact, especially if you are using a JSP 2.0 container, it's better to write what have become termed "scriptless" JSP pages. That is: pages that contain no java. No scriptlets, no declarations, no scriptlet expressions. Rather, these pages rely upon the EL (Expression Language), JSTL (JSP Standard Tag Library), JSP actions, and custom actions (formerly known as "custom tags") to perform their jobs.