* The preferred way to start a Swing application is
* wrap all construction in an invokeLater. Either of the following will
* work equally well:
* <pre>
* public class Main implements Runnable {
* public void run() {
* // Invoked on the event dispatch thread.
* // Construct and show GUI.
* }
* public static void main(String[] args) {
* SwingUtilities.invokeLater(new Main());
* }
* }
* </pre>
* Or:
* <pre>
* public class Main {
* Main() {
* // Invoked on the event dispatch thread.
* // Construct and show GUI.
* }
* public static void main(String[] args) {
* //Schedule a job for the event-dispatching thread:
* //creating and showing this application's GUI.
* SwingUtilities.invokeLater(new Runnable() {
* public void run() {
* new Main();
* }
* });
* }
* }
* </pre>
* This restriction applies to any models attached to Swing components.
* For example, if you have a TableModel attached to a JTable you should
* only modify the TableModel on the event dispatch thread. If you modify
* the model on a separate thread you run the risk of random exceptions and
* possible display corruption.
*

* More information on this topic can be found in the
* Swing
tutorial,
* in particular the section on
* How
to Use Threads.
*/

-Scott

swing@javadesktop.org wrote:
> Hi,
> I have noted that threading model is very important to Swing developers in several places, like in http://java.sun.com/javaone/sf/java_rock_star/romain_guy.jsp.
> Where can I learn more for the threading model of Swing?
> Thanks!
> [Message sent by forum member 'ylzhao' (ylzhao)]
>
> http://forums.java.net/jive/thread.jspa?messageID=117190
[/nobr]