if (mapping.getAttribute() != null)
{
if ("request".equals(mapping.getScope()))
request.removeAttribute(mapping.getAttribute());
else
session.removeAttribute(mapping.getAttribute());
}
I commented the above portion, now the old form is always there. Now, i have to bring the same page up for a different person, how would i clean the old form values. OR as a matter of fact, the very first time when the page comes up, the form doesn't have any value to initialize with. The session do have the values but there is no way i can initialize form values with these session values in the form class itself. Is there?
--On Monday, December 30, 2002 10:55 AM -0800 "Karr, David" <[EMAIL PROTECTED]> wrote:
If you don't put the form bean into the session, the values won't be there on the next request. Do you have the "scope" of the action set to "session" or "request"?-----Original Message----- From: Jain, Vikas [mailto:[EMAIL PROTECTED]] Sent: Monday, December 30, 2002 10:36 AM To: Struts Developers List Subject: RE: options collection problem You are right. But here is the confusing part, When getters are called (getNoticeStatus()) on the form associated with the page which has 'noticeStatus', they have null values. So, on the page i use session object to get my values and display them. While submitting the form the setters are called appropriately and sets the value. And now i am wondering, i am NOT benefitting from the getters at all. How do i put them to use. So that i dont have to use session values on the page. --On Monday, December 30, 2002 9:36 AM -0800 "Karr, David" <[EMAIL PROTECTED]> wrote: > The setter and getter for the "noticeStatus" property on your > form bean are the key to this. The setter is used when you > submit the form, and the getter is used to populate the > selected item. It would be useful to set a breakpoint in your > getter method, to first verify it is getting there, and then > to verify what value it is retrieving. It's possible the form > bean is just in request scope, which would mean the form bean > used to set the value at submit time would be a different > object from the bean used to populate the form. > >> -----Original Message----- >> From: Jain, Vikas [mailto:[EMAIL PROTECTED]] >> >> I am having trouble in displaying default or previous stored >> value while using the following: >> >> <html:select property="noticeStatus"> >> <html:options collection="someList" >> labelProperty="noticeStatusStrKey" >> property="noticeStatusStrValue"/> </html:select> >> >> >> Value is selected and set properly but next time it does not >> show the previous stored value. ?? > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> For > additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > --------------------------------------- Jain, Vikas Vanderbilt University Email: [EMAIL PROTECTED] -- 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]>
--------------------------------------- Jain, Vikas Vanderbilt University Email: [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
