Hi there, I'm getting increasingly frustrated at a weird Wicket behavior I don't seem to master. Use case, first: my user registration app has the typical registration work flow: enter some data, confirm, ask the user to check his email for a confirmation URL which, of course, is a Wicket-handled URL.
I'm using Firefox which is configured to open external links (links from other applications) on a new tab. When I get the confirmation email, usually I still have the original registration window open, so that when I click on the link in the mail message I get a fresh tab while still having a window with the original registration app. This is causing *major* headaches, since the corresponding page, for no apparent reason to me, gets called *twice*. This, in turn, means that the corresponding business logic (finalize the user registration) gets called twice, which really shouldn't happen. If you want to see this happening in front of your eyes, just download http://www.rabellino.it/quickstart.zip, which is a very quick and dirty wicket quickstart sample showing off what happens when you use multiple tabs (it's just a very simple static counter which gets incremented by 2 instead than 1 when called from an external link). Is this a known issue, and are there any workarounds? Thanks, -- Gianugo Rabellino _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
