I think its worth a try to resolve your problem, but I think it would
vastly increase efficiency if you could give a code example which
produces the error.
In fact i really had some similar exceptions in the beginning, which
in most cases could be dereferenced to some bug, made by myself like
the code is not that interesting or special.
I define a composite widget class and specify the .ui.xml and
everything UiBinder would need, and then instantiate that class 20
times. 18 or 19 of them will attach to the DOM without a problem (and
their element can therefore be found) but once or
I have recently started to use UiBinder as a way to define the UI. I
have previously defined my UI using either just Java code to build
panels and widgets or by (ab)using setInnerHTML.
I have never come across runtime exceptions when creating widgets
until using UiBinder. My UI will now throw
