Hmmm I think I got your concern, I had that issue once too, So ...
1. either you do it the stupid way to pass it through "request" by "request" or ...
2. store it on some persistence storage == db/file etc.
3. use a cookie ?
I want to highlight a few things:
(i) passing params/attributes (of Object,Vector or whatever) tru 1 level page-flow is OK.
(ii) common information can be store in application scope, e.g.: countries,common combo box values, table data, ...
(iv) login information, locale information to be stored in session.
I don't really know what you are trying to pass around, but if it is a user input ... and you don't use that information immediately in the next page ... there must be some problem with your flow. This is a web page, not a desktop application.
Do you understand my language? Haha, I'm found I'm so lost too ...
Anyway I would like to hear your feedback or show portion of your codes here, may be we can work something out ... :)
Good luck!
By Avatar Ng