No, in fact the problem that I was getting was the combination of other factors that had nothing to do with JGo: the use of a PropertyChangeEvent on a model to fire a change in the respective node and a Thread that constantly modified the model.
The main problem of refreshing the view was because I hadn’t instantiated correctly the PropertyChangeListener after I copied the node from a pallete to the view.
Then after I corrected this, I got one org.eclipse.swt.SWTException: Invalid thread access, because I cannot, normally, use a thread that modifies an UI component (in this case, the node). To do that, I must call the Display:syncExec or Display:asyncExec.
But thanks for your assistance.