I have a button that calls a method from the backing Bean. This method allows to extract data from parsing html code. While the method is running i have a dialog showing a progress bar and a command button Cancel
. I need when the user click the cancel button the method called by the extract button stops.
This is my html code:
<p:commandButton
value="Start" style="width: 12%;height: 100%"
update=":confirmPurchase, :confirmPurchaseTest, :mainform" id="extractbutton"
ajax="true" widgetVar="ButtonExtract"
actionListener="#{mailMB.searchEmails()}"
icon="ui-icon-disk" styleClass="ui-priority-primary"
onstart="blockUIWidget1.show();" oncomplete=" blockUIWidget1.hide();" />
<p:dialog widgetVar="blockUIWidget1" header="Hitonclick" modal="true"
resizable="false" closable="false">
<table border="0" style="width: 500px">
<tbody >
<tr>
<td>
<p:graphicImage url="pictures/loading81.gif" width="200" height="200" alt="animated-loading-bar"/>
</td>
<td>
<h:outputLabel value="Extracting is in progress. Please wait..."/>
<div align="center">
<p:commandButton value="Cancel" title="Cancel" />
</div>
</td>
</tr>
<div align="right">
</div>
</tbody>
</table>
</p:dialog>
And here is my searchEmails method in my sessionScoped Bean
public void searchEmails() throws Exception {
idCustomer = (String) session.getAttribute("idCustomer");
System.out.println(idCustomer + " this is it");
Customer customer = customerBusinessLocal.findById(idCustomer);
data = dataBusinessLocal.createData(new Date(), number, keyword, moteur, customer, State.REJECTED);
mails = mailBusinessLocal.createEmails(keyword, number, moteur, data);
System.out.println("Method was invoked");
}
How can i stop the searchEmails method from running via the cancel command button?
With your current architecture it's not going to be easy. By looking at your code it seems that you are calling two big operations that can't be aborted in the middle. You must break the work into small units and make the processing abortable.
The easiest solution that uses your current code could look something like this.
In JSF:
That said I'd recommend using executors and futures based approach for cleaner architecture. Then you can also implement a real progress bar not just an animated GIF spinner.
Another problem with performing a long operation in command handler is that eventually the HTTP request will time out.
A cleaner solution will look like this:
Then use an AJAX polling component to poll getPending to determine when it's done and hide the window.
See also:
ExecutorService with interrupt friendly tasks
ExecutorService
documentationInstead of directly calling the method, convert the method into an
ExecutorService
's task.You can use
Callable<Object>
if you want to return something.When you want call the method, submit that task to an
ExecutorService
.Keep a reference to the task.
A map should be a good idea to store multiple
Future
objects. You can of course go for something better if you want.Call cancel on the task whenever required.
Note:
Task should have suitable checks for thread interruption for proper cancellation.
To achieve this, refer to
Good luck.