Hebert Coelho wrote:You would need to use Ajax for that.
Is the last query taking to long? Or all the process take too much time?
Paul Clapham wrote:Have a look at this thread for a related question.
The initial request starts a thread running and puts a reference to the thread, or to some proxy for the thread, into the user's session.
Subsequent requests get the thread from the session. If it is still alive, the response says "Still running", otherwise the response says "Finished".
Of course you can expand on this basic structure to return the result of the long-running process, or to return the percentage complete if the long-running process can produce that information.
tinku rider wrote:it seems you are using the same servlet to generate the display view purpose also, this is happening because when the execution of the servlet completes then only we gets the view
it is not possible to get the view from the servlet in the middle of the execution and once again go back to the execution point, all container generates the view after complete execution of the servlet.
tinku rider wrote:how you want to generate the view? you have to explain in detail then only i can help you out
in the sense do you want to give the alert box to the user?
Rob Spoor wrote:There are two references there: Bayeux b and Channel c. As b has already been successfully used before (on line 16), that means that your Channel is null.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton