I'm not 100% sure, but I'm pretty sure that it would depend on your servlet container more than Wicket. The threads for handling requests are spun up by the servlet container before Wicket is ever handed the request. And typically these threads are pooled - so it wouldn't be *destroyed*. But you'll definitely need to do some testing on it to be sure.
-- Jeremy Thomerson http://www.wickettraining.com On Wed, Aug 19, 2009 at 3:03 AM, Ashika Umanga Umagiliya<auma...@biggjapan.com> wrote: > Greetings all, > > Please refer to image at : > http://i26.tinypic.com/11qi6o7.jpg > > I am going to invoke a webservice using Axis2 Client,asynchronically.To > getback the results, I am using a Callback handler in axis2. > > Within my page, I am going to create the Callback object > (axisCallbackHandler in picture) and call the axis2client which will create > a seperate thread for async access. > My concern is that what would happen if the user close the browser while > still axis2client-thread consuming the service?does the "wicket-thread" get > destroyed? > If thats the case,I want to send the results in an email ,if not display the > results in the wicket page. > > Thanks in advance > > > --------------------------------------------------------------------- > 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
