It is depend on what scope you specified for you from bean in the action mapping. My guess is you didn't specify the scope to be session, so when your action get submitted the controller look for the bean in the specified session( in this case it is not the session scope) and it doesn't find it there so it create one for you.
> -----Original Message----- > From: Struts Newsgroup [SMTP:[EMAIL PROTECTED]] > Sent: Thursday, May 09, 2002 2:10 PM > To: [EMAIL PROTECTED] > Subject: Problems with FormBeans > > Subject: Problems with FormBeans > From: Maurice Mills <[EMAIL PROTECTED]> > === > I am having a problem with my struts forms. > > I call an Action class to load a FormBean and put it in the session. > The bean is used to load the values on the form correctly. > > The problem occurs when the form is submitted. > > Instead of using the bean in the session, the RequestProcessor is > creating a new one. I see the constructor of my FormBean being called. > > Should it be using the one in the session, or creating a new one every > time? If the session bean is to be used, how do I make this work? If > not, how do I deal with nested lists of attributes of unknown length? > > Thanks, > Maury > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
