On Thu, 27 Jan 2005 11:40:45 -0500, Christopher Loschen <[EMAIL PROTECTED]> wrote: > Thanks for your advice! > > I've checked the ActionMappings and they all mention the request scope: > > <action path="/profile/personal_profile" > type="com.xxx.users.actions.GetCurrentUserProfileAction" scope="request" > name="userProfileForm" validate="false" > parameter=".main.profile.personalProfile"></action> > ... > > <!-- Email address updates --> > <action path="/profile/personal_profile/email" > type="com.xxx.users.actions.GetUserProfileAction" scope="request" > name="userProfileForm" validate="false" > parameter=".main.profile.personalProfile.email"></action> > <action path="/profile/personal_profile/email/update/confirm" > type="com.xxx.users.actions.ConfirmUpdateUser" scope="request" > name="userProfileForm" validate="true" input="update_company_user"> > <forward name="success" > path=".main.profile.personalProfile.email.update.confirm"/> > <forward name="error" path="/profile/personal_profile/email.do"/> > </action> > <action path="/profile/personal_profile/email/update/perform" > type="com.xxx.users.actions.UpdateCurrentUserAction" name="userProfileForm" > scope="request" validate="true"> > <forward name="success" path="/profile/personal_profile.do" > redirect="true"/> > <forward name="error" path="/profile/personal_profile/email.do"/> > </action> > > The userProfileForm maps to: > > <form-bean name="userProfileForm" > type="com.xxx.users.forms.UserProfileForm"/> > > and that class looks pretty normal: it extends ValidatorForm. The > GetCurrentUserProfile class extends xxxAction, which extends Action. Both of > the classes look pretty benign to me: neither explicitly places the form into > any particular context, so I presume that's left to the Action class, which my > mapping says should be putting it into request scope (I think). > > I'll bet it's staring me in the face, but I still don't see it. Do you see > anything I might have missed? >
After the update of the email you are redirecting to the (/profile/personal_profile.do) GetCurrentUserProfileAction. So, how does the GetCurrentUserProfileAction populate the form with the email address? Doesn't look like the GetCurrentUserProfileAction reads from the database for the new email address > > Thanks again for your help! > > >Can't promise this, but make SURE your Action Mappings specifically > >define the scope of your form bean. My HUNCH is that the one that > >displays the first time is in session scope, but your submit action is > >defining one in request scope. > > > >w > > > >Christopher Loschen wrote: > >>Hi all, > >>The action classes do seem to be updating the form correctly, but if > >>they were, I'd get the updated data, right? > >>Yours, > >>Chris > > > > > > Yours, > > Chris Loschen > [EMAIL PROTECTED] > > > ____________________________________________________________________ > > --------------------------------------------------------------------- > 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]
