Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 352345

Summary:

Duplicate entries in object mapping

Product:

[Technology] Jubula

Reporter:

Felix Ziesel <Felix.Ziesel>

Component:

Assignee:

Project Inbox <jubula.ui-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Oliver Goetz <Oliver.Goetz>

Severity:

critical

Priority:

CC:

alexandra.schladebeck, Marcel.Hein, markus.tiede

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Linux

Whiteboard:

Attachments:

Description	Flags
Stack trace	none
Screenshot after DND + Refresh	none
The Project with dublicate Component Names	none

Description Felix Ziesel

2011-07-18 09:33:56 EDT

To reproduce the bug you have to do the following things:

1. Map a component
2. use the component in a check for a check and in the following event handler (in my case another check)
3. rename the event handler test case
4. extract a test case from the first check (with the old name of the renamed one)
5. add the event handler to the extracted test case
6. remove the event handler from the parent test case.
7. Move the test cases one by one to the reused project

You can use the project of bug 352342 to see the result.
The mapping of component "Label (Usage Data Upload)" has three component names for the technical name:
* An id without any properties
* component name with this project as context
* component name with reused project as context

When I put the technical component back using DragAndDrop a Null-Pointer exception occurs (see attachment)
When pressing refresh afterward there are three components with the same name at the left side of editor.

Comment 1 Felix Ziesel

2011-07-18 09:34:46 EDT

Created attachment 199828 [details]
Stack trace

Comment 2 Felix Ziesel

2011-07-18 09:38:58 EDT

Created attachment 199830 [details]
Screenshot after DND + Refresh

Comment 3 Markus Tiede

2011-09-09 02:29:41 EDT

Could you please check whether this issue is still reproducible; also see bug 352711 comment 5.

Comment 4 Alexandra Schladebeck

2011-09-13 07:16:04 EDT

New image is in the manual

Comment 5 Alexandra Schladebeck

2011-09-13 07:22:44 EDT

Sorry, closed wrong bug by accident!

Comment 6 Alexandra Schladebeck

2011-09-14 08:29:32 EDT

This is still reproducible. Once the object map is in this state, other strange behaviour can be observed as well. However, deleting the technical name and sequentially deleting all component names then saving and reopening can produce an object map that at least looks correct (only one component name shown). Nevertheless, the issue of object maps in the case of move to external project should be analysed.

Comment 7 Alexandra Schladebeck

2013-11-19 06:06:19 EST

Since the steps to reproduce are not, in my estimation, the most likely path of doing things and there is a workaround, I'm closing this as wontfix.

Comment 8 Oliver Goetz

2013-11-19 09:58:33 EST

Closed due to comment 7

Comment 9 Marcel Hein

2014-04-10 04:31:17 EDT

I've had this problem again in our JavaFX Caa project, unfortunately I can't say if this situation was produced the same way as mentioned here, because I just found it like this.

When you break up the old mapping and map one of these with a component, you have to map all the duplicates again, which isn't possible and fails without any error message. But you still have the error that object mapping is incomplete, I've then deleted the duplicate component name and the error was gone and I could successfully execute the test which uses this comp name.

I will upload the exported project.

Comment 10 Marcel Hein

2014-04-10 04:33:18 EDT

Created attachment 241814 [details]
The Project with dublicate Component Names

Comment 11 Marcel Hein

2014-04-10 04:59:50 EDT

You can find some of the duplicates in the MainPage category.

Comment 12 Alexandra Schladebeck

2014-04-15 02:23:39 EDT

Thanks for the update Marcel. Since the original way of reproducing this was decided to be unusual, and we can't know whether the same steps or different ones led to this, and because you managed to fix it, I'm going to re-resolve this as wontfix. 

As always, if any other information or arguments become apparent, please comment and reopen.

Comment 13 Oliver Goetz

2014-04-15 02:48:51 EDT

Closed due to comment 12