Thanks for the suggestion. Since our Wicket application is presently a singular page, I can kind of imagine how this could work assuming the 'iframe' is embedded in the outermost part of the HTML (thus lies outside of any potential AJAX refreshes by Wicket). It will also mean that we must stick to this singular page (i.e. no page changes as part of the user workflow), otherwise I can imagine the 'iframe' would be lost/reset.
So I'm guessing this is how it would work: - have a form that submits to the separate servlet being embedded in the hidden iframe - the fields for that hidden iframe form correspond directly to what the user is expected to input via a Wicket form - upon hitting the submit button on the Wicket form, it copies all the contents of the fields (using JS?) from the Wicket form to the hidden iframe form - finally we trigger the submit on the hidden iframe form using JS It sounds like it has potential, but not as clean/quick to implement as I was originally hoping for. Would anyone perchance have already tried this strategy and got it working? Kind Regards, Eric. ----- Eric is learning how to use Wicket and enjoying the experience so far... -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Asynchronous-File-Uploads-tp2541855p3086678.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
