Michael
At 02:44 PM 3/4/2004, you wrote:
Hi all,
I'm working on a web app where I have my JSPs hidden beneath WEB-INF. In doing so, I of course have actions which RequestDispatch those pages to the user. In doing this I am running into a problem where beans in those returned JSPs are not getting updated when they are returned from other actions. For example, on my login screen lets say I have a bean "junkbean" that hold some data, which is loaded in LoginAction. That bean has data in it when I call /login.do directly. When I complete a form on that screen and submit it to /update.do, I would like to return the user to the /login.do screen. But when I do that, "junkbean" is nowhere to be found, as if the action behind /login.do is not doing anything. But, if I call /login.do directly, then "junkbean" is there with all it's data.
How can I get my action behind /index.do (or any similar action that gets data, then RequestDispatches a JSP back to the user) to execute so that I can have my updated beans present? If this is not the ideal way to do it, what would be a better design for doing this sort of thing? Essentially I want to hide all my JSPs behind WEB-INF, but I would still like to have them updated after I submit forms and return action paths, which load those JSPs.
Thanks so much for your help, and I look forward to receiving your advice.
Andy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]