Hi Johan, Thanks.
How is it possible that this is true with any ImageButton constructor: (getImageResource() == null && localizedImageResource.isStateless()) On Fri, 20 Aug 2010 13:25:11 +0200, you wrote: >an image button can be stateless: > > protected boolean getStatelessHint() > { > return getImageResource() == null && > localizedImageResource.isStateless(); > } > >but that must be true. > >On Fri, Aug 20, 2010 at 13:19, <b...@actrix.gen.nz> wrote: >> Hi, >> >> I had a stateless login form that did actually not expire >> >> ... until I added an image as submit button. >> >> Sorry to raise this topic again, but AFAIK this has not been answered >> yet: >> >> ImageButton - always stateful ? >> >> http://apache-wicket.1842946.n4.nabble.com/ImageButton-always-stateful-td1875620.html >> >> I feel I am forced to use ImageButton because I need it as >> IFormSubmittingComponent so I can distinguish between two different >> submit methods. >> >> It is really as simple as two image buttons on the form - one as >> login, the other as "forgot password" >> >> Many thanks for any ideas! >> >> Bernard >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > >--------------------------------------------------------------------- >To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >For additional commands, e-mail: users-h...@wicket.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org