swingworker

From the documentation for SecondaryLoop , it is not clear when you should use this new feature instead of a SwingWorker , a few examples of interesting cases would be useful. The intent of SecondaryLoop is basically the same as SwingWorker. However, using SecondaryLoop can be less hairy than chaining together multiple SwingWorkers. Take a look at Hidden Java 7 Features – SecondaryLoop for a detailed explanation & example. 来源： https://stackoverflow.com/questions/10196809/secondaryloop-instead-of-swingworker

I use SwingWorker in Java 6 to avoid running long-running code on the event dispatch thread. If the call to get() in my done() method returns an exception, what is an appropriate way of handling the exception? I'm particularly concerned about possible InterruptedExceptions. The JavaDoc example simply ignores the exception but I've learnt over the years that swallowing exceptions leads to hard-to-debug code. A sample usage is as follows: new SwingWorker<String, Void>() { @Override protected String doInBackground() throws Exception { // do long-running calculation return result; } @Override

With reference to the java.util.concurrent package and the Future interface I notice (unless I am mistaken) that the ability to start a lengthy tasks and be able to query on the progress only comes with the SwingWorker implementing class. This begs the following question: Is there a way, in a non-GUI, non-Swing application (imaging a console application) to start a lengthy task in the background and allow the other threads to inspect the progress ? It seems to me that there is no reason why this capability should be limited to swing / GUI applications. Otherwise, the only available option, the

I've been struggling with the usability problem of SwingWorker eating any exceptions thrown in the background task, for example, described on this SO thread . That thread gives a nice description of the problem, but doesn't discuss recovering the original exception. The applet I've been handed needs to propagate the exception upwards. But I haven't been able to even catch it. I'm using the SimpleSwingWorker wrapper class from this blog entry specifically to try and address this issue. It's a fairly small class but I'll repost it at the end here just for reference. The calling code looks

I have a problem as follows: I've written a simple minimalistic Application that utilizes the SWT for the GUI. In a specific tab, where it displays a table that get's filled with Informition via a REST Api Call. Additionaly, i have another method to export this table into a CSV-file. This works absolutely fine. Now I need some kind of autoupdate/-export for which I implemented a Swing-Worker like this: protected class AutoExportWorker extends SwingWorker<Integer, String> { @Override public Integer doInBackground() throws Exception { System.out.println("Worker Start!"); while (true) { System