Setting ID breaks object boundaries

[ihme]

Observed with smartgwt 2.3 and gwt 2.6.

I am new to smartgwt development and I come from a swing background. So I may have some baggage of invalid assumptions. If so, please let me know.

The following piece of code has strange - to my mind at least - effects:

        TabSet tabs = new TabSet();
        
        tabs.setID("test");
        
        tabs.addTab(new Tab("test1"));
        
        masterlayout.draw();
        
        masterlayout.removeMember(tabs);
        
        TabSet tabs2 = new TabSet();
        
        tabs2.setID("test");
        
        tabs2.addTab(new Tab("test2"));
        
        masterlayout.addMember(tabs2);

On the UI you will see a tab set with two tabs "test1" and "test2". The key statement in the code above is setting the tabsets to the same id.

I thought that this would be ok since at any one time in the live UI tree, the ID is unique.

I also thought that setting this ID would help me in finding the "widgets" by their ID in the final output (for test automation purposes), which also wasn't the case.

If someone could elaborate on what this ID is, what it is used for, which constraints apply, that would be greatly appreciated.

[Isomorphic]

Just to let you know, we won't be looking at any reports of issues with a version that ancient. Let us know if you can reproduce on the latest available versions.