Honestly, I simply cannot grasp the problem. Our site works like this:
1. User fills form. 2. User submits form to Wicket site. 3. Wicket site analyzes the submitted form and constructs a PageParameters map. 4. Wicket site redirects the user to a payment processing server using the PageParameters. If "10 forms in the same page." are in stage 1-2 it does not matter, you can make 3-4 as simple as you want. Maybe you could describe your process in more detail? ** Martin 2009/1/14 Mathias P.W Nilsson <[email protected]>: > > This is what I'm doing ( via an javascript call from wicket ajax after the > form is validated). Problem is that the model must be emptied when the form > is submitted ( cart, order ) and then the page get's rerendered. It's all > fussy. > > 10 forms in the same page. Must be a smarter solution. > -- > View this message in context: > http://www.nabble.com/Advice-on-payment-options-with-wicket-tp21452753p21461128.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]
