Summary: | IllegalStateException: drag and drop entity to diagram editor | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [WebTools] Dali JPA Tools | Reporter: | Nan Li <nan.n.li> | ||||||||
Component: | Diagram Editor | Assignee: | Project Inbox <dali.diagrameditor-inbox> | ||||||||
Status: | RESOLVED FIXED | QA Contact: | Petya Sabeva <petya.sabeva> | ||||||||
Severity: | major | ||||||||||
Priority: | P1 | CC: | kaloyan, neil.hauge, tranle1 | ||||||||
Version: | unspecified | Flags: | neil.hauge:
pmc_approved?
(david_williams) neil.hauge: pmc_approved? (raghunathan.srinivasan) neil.hauge: pmc_approved? (naci.dai) neil.hauge: pmc_approved? (deboer) neil.hauge: pmc_approved+ neil.hauge: pmc_approved? (kaloyan) neil.hauge: pmc_approved? (cbridgha) neil.hauge: review+ |
||||||||
Target Milestone: | 3.2 RC2 | ||||||||||
Hardware: | PC | ||||||||||
OS: | Windows 7 | ||||||||||
Whiteboard: | PMC | ||||||||||
Attachments: |
|
Description
Nan Li
2012-05-25 12:00:10 EDT
Created attachment 216296 [details]
IllegalStateException stack trace
Created attachment 216297 [details]
StackOverflowError stack trace
I have reproduced this in the RC2 candidate. Created attachment 216350 [details]
Fix IlligalStateException
The same exception occurs when an entity is removed from the diagram (with and without saving the changes). The patch fixes all three issues.
All automated tests have been passed successfully and the fix is tested manually. The changes are small, so I think the risk of applying the patch is low.
Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such. P1, drag and drop does not work in the diagram editor. This is the standard use case. Is there a work-around? If so, why do you believe the work-around is insufficient? No workaround. How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? Automated and manual tests. Give a brief technical overview. Who has reviewed this fix? This bug is a result of the move to Graphiti 0.9, where apparently some of the transaction mechanics have changed. This patch updates the code to conform to this. What is the risk associated with this fix? Medium to high risk. Affects core aspects of functionality. Given that current state is unusable, this risk is acceptable. Approving this so we can move forward with a re-spin. Patch committed and released. Resolved in RC2. |