Community
Participate
Working Groups
To reproduce: 1. Create new diagram 2. Add new Entity1 3. Add new Entity2 4. Create OneToMany from Entity1 to Entity2 which will create a field named "entity2" of type java.util.Collection<Entity2> in Entity1. 5. Right click on entity2 field of Entity1 and select "Refactor Attribute Type.." 6. Replace "java.util.Collection" with "java.util.List" and press Ok. 7. OneToMany relationship drops from the diagram and the field in the Entity1.java file is now just java.util.List with no generic--probably why it was dropped from the diagram as the list type is unknown.
After the refactor you also get an error from Dali complaining that the target entity of the OneToMany is unknown.
That's because the type of the collection elements is not managed by the refactoring dialog and after refactoring the new type attribute is java.util.List instead of java.util.List<Entity2>.
Yes, that's the bug I'm reporting. The refactoring doesn't preserve the collection's element type.
Agreed. I've targetted it for 0.7
Created attachment 189594 [details] patch
The bug is important, so I've retargetted it for M6 and submitted the patch
Verified in Build I-3.3.0-20110414085808 Verified type is not dropped from diagram when changed from collection to list. See the link to view test steps for verification. http://wiki.eclipse.org/Dali_3.0_M6