Busy Plugin

Paul Coward wrote:

I have noticed that cancelling the busy jar quickly, in processes that take some time, and reopening numerous times will lock up the busy jar causing it to no longer show.

Also I'm noticing strange behaviour when our users try to print a report. In this situation we open a dialogue to get further user input and when the user clicks ok we make a call through the plugin. This call basically just sets up ids and paramaters then makes a jasper report run report call.
The issue here is that the jasper report will open a dialog for the user to open or save the generated report, and the busy plugin seems to hold that process until the user tries to print another report (where the parameter dialog needs to be opened for it to show the open/save dialog).

I'm not sure about the reopening numerous times, haven't been able to reproduce with the same setup...
Perhaps you would have a case where that happens so that I could have a look?

For the second part, I'm sorry to say that this will simply not work.
You said it yourself: "the jasper report will open a dialog". But the busy jar is blocking the UI, and the call to the process is synchronous, the only call that I managed to do (with a lot of jumping the hoops, was an Ajax call to a servlet defined by the plugin, which set an AtomicBoolean in a ConcurrentHashMap that is in turn queried by the client via a Remote service, this works fine when all that is done is setting a boolean for cancel, but this will not allow more complex interactions with the browser since Wicket is blocking the calls anyway, queuing them to run after the process method is finished).

v2.2 doesn't show this behavior as frequently. Still from time to time, it seems the process is called before the web UI has been refreshed, it seems to be a problem of sequential call in the Servoy executor. Not sure if it's fixable, but the refactored version v2.2 shows a definite improvement here.

I think this one is fixed with v2.2.4 - feel free to reopen if you see otherwise.