Wicket replaces & with & on any place in markup it produces. That's how markup document works. & is a beginning of entity and must be escaped. In your case the escaping seems to be done twice. That might mean a bug in wicket. In that case the proper thing would be creating a jira issue instead of calling the framework dumb. And I doubt anyone would bother to be kidding you.
-Matej On Dec 21, 2007 7:23 PM, fattymelt <[EMAIL PROTECTED]> wrote: > > I've been debugging a (hopefully) unrelated problem when I came across > this... > > Someone submits "passw&rd" as a password in my login form and the back-end > gets it as passw&amp;rd > > Are you kidding me? Why would that be happening? > -- > View this message in context: > http://www.nabble.com/Wicket-really-dumb--Converting---to--amp--in-password-fields--tp14460118p14460118.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
