[concurrency-interest] Reason behind making execute method of SwingWorker as final ?

Joe Bowbeer joe.bowbeer at gmail.com
Mon Mar 2 11:00:10 EST 2009


I see your point.  For your purposes, it would be nice if you could supply
your own executor service, or even thread factory.  If only the
getWorkerExecutorService method was not private static...

Manually submitting the SwingWorker to a custom executor was the solution
envisioned by the designers.

See related discussion:


I suggest you contact Igor Kushnirskiy and/or whoever is currently
maintaining SwingWorker.


On Sun, Mar 1, 2009 at 9:52 PM, Mallikarjunaiah, Praveena wrote:

> Hi,
> I was wondering why execute() method of SwingWorker is made final. In
> some cases,  I want certain type of SwingWorker's to use a specific
> thread.
> Currently, this can be done by explicitly putting the worker in a custom
> executor service.  I would like put this logic in execute() method so
> that
> Generators of SwingWorker need not worry how to execute them.
> Am I missing something here ?
> Thanks
> Praveena
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20090302/19ef68f0/attachment.html>

More information about the Concurrency-interest mailing list