Martijn Dashorst wrote: > It is configurable: don't use PasswordTextField but TextField instead.
No. If you try to use a TextField, then wicket will insist that you convert your HTML to use <input type="text"/> instead of <input type="password"/> - and thus lose the masked password entry capabilities (i.e., echoing "*" characters). > 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 Well, I guess I don't have a problem with that. But I think that there's a bug going on here. I just filed it at: https://issues.apache.org/jira/browse/WICKET-768 DR ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
