File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes JSP and the fly likes Persisting Drop down Value Between Screens Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » JSP
Bookmark "Persisting Drop down Value Between Screens" Watch "Persisting Drop down Value Between Screens" New topic

Persisting Drop down Value Between Screens

Rohit Dhodapkar
Ranch Hand

Joined: Apr 27, 2006
Posts: 38
I have a jsp page which shows customer information . As the number of records can be numerous we have implemented pagination (20 records on a page) . So user can hit on first next ,last , previous . now on each row in the customer record I have a drop down(combo box) . Now what I want is that when user selects something in the combo box and navigates to the next page and then comes back he should get all the selected values in place . can smbody propose some method of doing this..
Bear Bibeault
Author and ninkuma

Joined: Jan 10, 2002
Posts: 63869

Use the selected attribute on the option that is to be selected in the dropdown.

[Asking smart questions] [About Bear] [Books by Bear]
Rohit Dhodapkar
Ranch Hand

Joined: Apr 27, 2006
Posts: 38
Bear how do I store these selections ? . I mean should I store them in session,request or some other thing . If yes How should I go about it..
Travis Hein
Ranch Hand

Joined: Jun 06, 2006
Posts: 161
if you are using strictly servlet, and the selection from the form goes from jsp -> servlet -> jsp, using the request parameters is usually ok.

since you want to have things selected,then go to another page, then come back to this page and have them selected again, storing on the session attribute is probably more helpful; otherwise you would have to implement the hidden fields on the second page to store the values, this is not a good thing to maintain.

i assume from having a select on each row of the table would mean you need to have dynamic / different names for each row (i.e. select_1, select_2).

I would then recommend making a bean, perhaps just an instance of a hashtable, and stuffing this onto the session attributes, and it will contain the state for all the select options on your screen.
this way
- there is only 1 session attribute to get for each list screen, the values of the hashtable key: the name of the select / combo box, value: the id of the selected option.
- if you have other table list screens that would possibly have different sets of selected things in the future, each of screen can can store the selected combobox values independently

Error: Keyboard not attached. Press F1 to continue.
I agree. Here's the link:
subject: Persisting Drop down Value Between Screens
It's not a secret anymore!