| Summary: | Exception in error log while renaming entity | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] Dali JPA Tools | Reporter: | Stefan Dimov <stefan.dimov> | ||||
| Component: | Diagram Editor | Assignee: | Stefan Dimov <stefan.dimov> | ||||
| Status: | VERIFIED FIXED | QA Contact: | Stefan Dimov <stefan.dimov> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | jolene.moffitt, neil.hauge | ||||
| Version: | 3.0 | Flags: | stefan.dimov:
review+
|
||||
| Target Milestone: | 3.0.1 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Stefan Dimov
Created attachment 197115 [details]
fix
This is not a real error, but it would create a bad impression in the user that's why it's good to be fixed. No workaround. The fix was tested manually and all the exisitng JUnit tests are passing successfully. The exception is being logged during trial to save of non-existing resource. Actually everything is fine. The fix just ignores the exception when the corresponding resource is not accessible anymore. The risk is low, because the fix is very small and doesn't change the existing functionality. It just ignores the exception in some cases. I agree that this looks bad, but given the lower severity, probably not a candidate for RC4, even though the fix risk is low. Ok ... it was worth trying :) Perhaps 3.0.1? (In reply to comment #4) > Ok ... it was worth trying :) Perhaps 3.0.1? Certainly! patch submitted in R3_0_maintenance Patch also submitted in HEAD Verified in Build I-3.4.0-20110805150738 Verified no error appears in the error log when you rename the entity name in the diagram editor. See the link to view test steps for verification. http://wiki.eclipse.org/Dali_3.0.1 |