OK, the picture I have of your page/action flow is:

(1)indexaction -> (2)index.jsp -> (3)LogonAction -> (4)IndexAction -> (5)(not sure 
here if this is index.jsp or login.jsp)

If that is incorrect, please post the correct flow.  From the flow above though, 
junkbean is created in (1) and and is out of scope after the request expires following 
(2).  So LogonAction in (3) doesn't have access to the first junkbean unless it is 
added back to the request; if it tries to use it otherwise, without creating it, I 
would expect an error like you are experiencing.  IndexAction in (4) recreates the 
bean, does it not?  And then puts it in the request again?  If it doesn't, there would 
be no junk bean in the request in (5).  

:-> -----Original Message-----
:-> From: Andy Engle [mailto:[EMAIL PROTECTED]
:-> Sent: Thursday, March 04, 2004 5:45 PM
:-> To: Struts Users Mailing List
:-> Subject: RE: Returning fully-stocked Actions/JSPs from other Actions
:-> 
:-> 
:-> Randy Dillon <[EMAIL PROTECTED]> wrote:
:-> 
:-> > ... Your first request scope ends once index.jsp loads; 
:-> if you want
:-> > to use the junkbean again after that, you have to save it again,
:-> > either in the new request or in the session (or possibly other
:-> > places, but those are the 2 most obvious).
:-> 
:-> Right -- I am putting it in the request scope in the second action,
:-> which is what LogonAction forwards to after it's finished.
:-> 
:-> 
:-> > So LogonAction would only be able to get junkbean from 
:-> the request if
:-> > index.jsp put it there (again).
:-> 
:-> LogonAction doesn't need junkbean.  It only needs to forward to
:-> IndexAction, which it is doing.  But when I get to 
:-> IndexAction (which
:-> loads index.jsp), it doesn't seem to be populating the bean 
:-> with data
:-> for index.jsp to access, hence the problem.  It seems to me that it
:-> should, hence my initial question.
:-> 
:-> 
:-> Thanks,
:-> 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]

Reply via email to