Problems with multiple threads and GUI refresh in Java

[Devabrata]

I try to outsource just a little longer lasting function in its own thread (so far tried on Thread, Runnable or Swing workers) to keep the surface during the process to use. The function runs smoothly in the background, now I got the problem that at the end of the run () method, the surface should be redrawn (refresh ()), in order to represent the result of the background function, and since I get so far always an exception:
org.eclipse.swt.SWTException: Invalid thread access

Browsing the Internet I have found some evidence that there may be problems if one tries to change a background thread from the surface or update. Unfortunately, none of it (usually works only sparingly) above alternatives or not matched the rest of the program. I read somewhere that one of the surface suggest a refresh can, which will then (eventually) run from the actual surface thread, but unfortunately was not described how to do it. Now I hope this maybe someone has an idea how this problem could be solved. Please help me to resolve this problem.

[Khushal]

Here time is a code snippet:

setSearching (true); 

RunSearch = new Runnable Runnable () ( 

@ Override 
public void run () ( 

Entry current = langugeFileManager 
. GetEntryForKey (getCurrentKey ()); 

setSearching (false); 
viewer.refresh (); 

) 

);

The viewer is to be refreshed is a org.eclipse.jface.viewers.TableViewer (I program a EclipsePlugin). If I comment out the refresh line the program runs without error, but then unfortunately no update of the view.

[Adley]

The Eclipse code book says, "You need the (SWT) Display instance, fire up the runnable asynchronously there.

RunSearch = new Runnable Runnable () ( 
... 
); 
display.asyncExec (runSearch);

The Swing event queue is not for the SWT.

[PARRISH]

It is really the Eclipse objects. Some of these are only by the thread calling problems, which she has created. Since my thread so only after the application accessing it at some point, the access could not be allowed. The solution is relatively simple. I just have the line

Event Queue. InvokeLater (runSearch);

against the line

Display.getCurrent (). AsyncExec (runSearch);

been replaced and the thing runs like it should. The display (org.eclipse.swt.widgets.Display) seems to be the only way to access the objects and asynchronously.