It is configurable: don't use PasswordTextField but TextField instead. The reason behind PTF's encryption is that we want to provide a secure solution out-of-the-box. You can circumvent it, but then *you* need to open up Pandorra's box, not us. Same with escaping markup while outputting model values: the default is safe.
Martijn On 7/19/07, David Rosenstrauch <[EMAIL PROTECTED]> wrote: > Just wondering: anyone know what's the reason behind 1) making > PasswordTextField's automatically encrypting their contents by default, > and 2) making this not configurable? > > I lost several hours debugging tonight till I finally pinpointed this as > the cause of my bug. > > TIA, > > DR > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > -- Wicket joins the Apache Software Foundation as Apache Wicket Apache Wicket 1.3.0-beta2 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta2/ ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
