Strange WindowBuilder error

[Olivercomputing]

Development context: Mac OS X 10.6, Eclipse Helios

I opened up a project for the first time in several months, after updating GWT SDK, WindowBuilder, and SmartGWT (v2.2, not the latest v2.4 which WindowBuilder says it cannot handle, unfortunately.) Now I can't open my source in the WindowBuilder design view. I get an error I've never seen before:

WindowBuilder internal error
WindowBuilder encountered unexpected internal error. Please contact support.
java.lang.RunTimeExcception: Failed to invoked native method:
@com.google.gwt.dom.client.DOMImpl::getParentElement(Lcom/google/gwt/dom/client/Node;) with 1 arguments.

To try to isolate the problem, I created a new workspace and a new GWT Web Application Project, then added SmartGWT attributes to the client file. I can reproduce the problem in this simple project by simply adding a VLayout object underneath the rootPanel:

VLayout layout = new VLayout();
layout.setSize("98%", "90%");
rootPanel.add(layout, 0, 57);

This was done inside the Designer itself. However, when I switch back to source view, make a semantic-less change (new linefeed) to cause a re-parse, I get the above error.

I don't know if anything other than VLayout is causing the problem, but it is enough to stop my development.

Is there a way to load earlier versions of WindowBuilder? I had also tried going back to earlier versions of GWT and SmartGWT but the problem appears to be within WindowBuilder.

[Eric Clayberg]

We need to see your complete Eclipse ".log" file and a complete test case in order to help.

It is not clear from the information you have provided whether the problem is in WindowBuilder or not.

Please use the "Contact Support" button to submit the problem so that we can properly analyze it.

[Olivercomputing]

I just sent it, including the entire project (if the checkbox worked.)

[Eric Clayberg]

We were not able to reproduce this exception, but we did notice that this example does not work at runtime either. This appears to be a SmartGWT problem, so we would recommend not mixing standard GWT widgets with SmartGWT widgets. This does not appear to be a GWT Designer issue.