Effective JavaFX Architecture Part 3 - Asynchronous calls, Command Pattern and Testability

In the previous installment of Effective Architecture, I covered TDD with Model-View-Presenter. However the code I presented had synchronous server calls. In JavaFX (like Swing), the UI code runs in the Event Dispatch Thread (EDT). It is unwise to block the EDT. Hence it is encouraged to execute all server calls on a separate thread. SwingWorker Swing provides SwingWorker to execute tasks off the EDT. SwingWorker also allows switching to EDT for things like setting the UI data etc. A snippet is shown below.  When a button is pressed, the SwingWorker executes the code in doInBackground() in background. When completed, the code returns the data as an Object. The SwingWorker then calls process() and done() on the EDT, to allow the user code to update the UI etc. Listing 1. SwingWorker final JButton button = new JButton("Save");ActionListener l = new ActionListener() {    public void actionPerformed(ActionEvent e) {    SwingWorker worker = new SwingWorker() {        protected Object doInBackground() throws InterruptedException {          //connect to server amd get data          return data;        }        protected void process(Object data) {          //update ui...

Date: July, 23 2010
Url: http://www.java.net/blog/srikanth/archive/2010/07/22/effective-javafx-architecture-part-3-asynchronous-calls-command-pat

Others News