Hi again, This is how I interpreted your last post Jeremy (please see attached code fragments: http://apache-wicket.1842946.n4.nabble.com/file/n3081409/TestingServlet.txt TestingServlet.txt )
The new approach appears to trigger the separate servlet, but the problem is that it also redirects the browser to the separate servlet's URL (and confirms my suspicion that "the Wicket application loses control" as I queried in a previous post). The requirements I'm trying to achieve are: - The Wicket application accepts parameters from the user, potentially including a file upload. - When the user hits submit, some processing needs to be done in the background to update the backend (e.g. decode and import the contents of the file). - However, the user should be allowed to continue doing other things in the Wicket application. - The user will be notified via email that the background processing has been completed and then they can come back to interact with the newly created information. So am I still approaching this correctly? Thanks in advanced, Eric. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Asynchronous-File-Uploads-tp2541855p3081409.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
