| Summary: | Refactoring Collection Type Drops Generic from definition and deletes from Diagram | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] Dali JPA Tools | Reporter: | Shaun Smith <shaun.smith> | ||||
| Component: | Diagram Editor | Assignee: | Stefan Dimov <stefan.dimov> | ||||
| Status: | VERIFIED FIXED | QA Contact: | Stefan Dimov <stefan.dimov> | ||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | jolene.moffitt | ||||
| Version: | 0.5 | ||||||
| Target Milestone: | 3.0 M6 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Shaun Smith
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 |