> That's an interesting idea; the current value could, in fact, be > stored into form data (that's "relatively" secure).
I could be wrong, but isn't the"form data" you are talking about stored in a hidden field on the page? That kind of talk could get Tapestry5 banned from my day job! It's hard enough to get new stuff through a security review when they have to look hard for holes :) > Alternately, the > password field could be changed to only update its value parameter if > the submitted value is non-blank (that's probably more useful). And also more likely to get through a security review. Josh On Fri, May 23, 2008 at 8:51 AM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > That's an interesting idea; the current value could, in fact, be > stored into form data (that's "relatively" secure). Alternately, the > password field could be changed to only update its value parameter if > the submitted value is non-blank (that's probably more useful). > > On Fri, May 23, 2008 at 8:09 AM, Dan Adams <[EMAIL PROTECTED]> wrote: >> Yeah, that was my question. Do you have to create a separate field outside >> your bean and then update manually if it hasn't changed? Or is there a way >> that the field could be smart enough to store the value in the session or >> something and then update the bean value only when the user enters one. >> >> Dan Adams >> Senior Software Engineer >> Interactive Factory >> p: 617.235.5857 >> >> ----- Original Message ----- >> From: "Joachim Van der Auwera" <[EMAIL PROTECTED]> >> To: "Tapestry users" <[email protected]> >> Sent: Friday, May 23, 2008 8:57:30 AM (GMT-0500) America/New_York >> Subject: Re: Use of passwordfield? >> >> Dan, >> >> This component does not display the previous value if there is one and >> hides the input. This is important as view source would otherwise reveal >> the passwords. >> >> The only thing you need to be careful about is that it will update your >> password field in the bean to null when no new value was given by the >> user. You probably don't want passwords to be reset like that. >> >> Kind regards, >> Joachim >> >> Dan Adams wrote: >>> To ask a dumb question: what's the use of the passwordfield component since >>> it doesn't output a value? I have a 'edit user' page where you have >>> password and 'confirm password' fields. When you submit the form it resets >>> the value to empty if you don't enter anything. >>> >>> Dan Adams >>> Senior Software Engineer >>> Interactive Factory >>> p: 617.235.5857 >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >> >> >> -- >> Joachim Van der Auwera >> PROGS bvba, progs.be >> >> >> --------------------------------------------------------------------- >> 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] >> >> > > > > -- > Howard M. Lewis Ship > > Creator Apache Tapestry and Apache HiveMind > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- -- TheDailyTube.com. Sign up and get the best new videos on the internet delivered fresh to your inbox. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
