Jubula thinks component name still exists after deletionhttps://www.eclipse.org/forums/index.php/mv/msg/488304/1061487/#msg_1061487
However, when I tried to create the same name in the other AUT's OM editor, it wouldn't let me because it said the component name already exists. I also noticed that the name still shows up under "Used Component Names" in the Component Name Browser (but not under "Assigned Names" in the OM Editor). When I right-click it in the browser and select "Show where used", nothing comes up, so I assume that its presence in the browser is erroneous.

Is there any trick whereby I can make this component name go away completely, or at least be recognized as unassigned so that I can re-assign it? Or is this more likely a database-end problem that I won't be able to fix in Jubula? If there is another trick that will allow me to avoid having this happen again, that would also be helpful.

Thanks!]]>David Hickernell2013-05-31T22:27:14-00:00Re: Jubula thinks component name still exists after deletionhttps://www.eclipse.org/forums/index.php/mv/msg/488304/1061861/#msg_1061861
It sounds a bit like it could be a refresh problem - does refreshing the project lead to the component name being placed under "Unused component names"?

HTH,
Alex]]>Alexandra Schladebeck2013-06-04T12:11:05-00:00Re: Jubula thinks component name still exists after deletionhttps://www.eclipse.org/forums/index.php/mv/msg/488304/1061912/#msg_1061912
Note: the project has been reconfigured so that there is only one AUT, as there should have been (the two that existed before were two versions of the same AUT). I think that may have fixed this particular instance of the problem, but I remember having seen a similar issue before, so having a possible remedy would still be helpful.

Thanks!]]>David Hickernell2013-06-04T16:43:11-00:00Re: Jubula thinks component name still exists after deletionhttps://www.eclipse.org/forums/index.php/mv/msg/488304/1062305/#msg_1062305
Sorry for the confusion - the project refresh can be triggered from the menu or from within the Test Suite Browser with F5.